DataForSEO
Keywords Data Bing Search Volume History
This endpoint will provide you with historical search volume data for up to 1000 keywords in one request. You can get search volume for keywords in monthly, weekly, or daily format and specify the device type.
Usage based DataForSEOSEOdataforseo/keywords-data-bing-search-volume-historyActive
Use this tool with your agent
Give this to your agent
Use my connected Agentik MCP server. I want to use the tool dataforseo/keywords-data-bing-search-volume-history (Keywords Data Bing Search Volume History). Call inspect_tool with {"tool_id": "dataforseo/keywords-data-bing-search-volume-history"} first and tell me the price before anything runs. Ask me for the inputs it needs; never invent values, IDs or file URLs. When I confirm, call run_tool with tool_id "dataforseo/keywords-data-bing-search-volume-history" and my inputs, follow it with get_run if it is still running, and give me the result and the price Agentik reports. If the tool is unavailable, say so and use discover_tools to propose an alternative.Show the prompt
Paste it into Claude, ChatGPT or Codex: your agent takes it from there, and shows the price before it runs.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
keywords | string[] | Yes | keywords required field The maximum number of keywords you can specify: 1000 The maximum number of characters for each keyword: 100 the specified keywords will be converted to lowercase, data will be provided in a separate arraylearn more a |
location_name | string | No | full name of search engine location required field if you don't specify location_code or location_coordinate if you use this field, you don't need to specify location_code or location_coordinate you can receive the list of available locatio |
location_code | integer | No | search engine location code required field if you don't specify location_name or location_coordinate if you use this field, you don't need to specify location_name or location_coordinate you can receive the list of available locations of th |
location_coordinate | string | No | GPS coordinates of a location required field if you don't specify location_name or location_code if you use this field, you don't need to specify location_name or location_code location_coordinate parameter should be specified in the "latit |
language_name | string | No | full name of search engine language required field if you don't specify language_code if you use this field, you don't need to specify language_code you can receive the list of available languages of the search engines with their language_c |
language_code | string | No | search engine language code required field if you don't specify language_name if you use this field, you don't need to specify language_name you can receive the list of available languages of the search engines with their language_code by m |
device | string[] | No | device types optional field specify this field if you want to get the data for a particular device types possible values: mobile, desktop, tablet, non_smartphones default value: ["mobile", "desktop", "tablet", "non_smartphones"] |
period | string | No | aggregates the returned data to a certain time period optional field specify this field if you want to get the data in monthly, weekly or daily formatpossible values: monthly, weekly, dailymonthly - returns data up to past 24 months weekly |
date_from | string | No | starting date of the time range optional field minimum value: 24 months back from today’s date; if Status endpoint returns false in the actual_data field, date_from can be set to the month before last and prior; if Status endpoint returns t |
date_to | string | No | ending date of the time range optional fieldminimum value: two years back from today’s date; maximum value: one day from today's date; date format: "yyyy-mm-dd" example: "2020-03-15"Note: we do not recommend using a custom time rangeNote 2: |
tag | string | No | user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response |
How your agent calls it
First inspect_tool for the current schema and price, then run_tool with the published example after confirming your inputs:
{
"tool_id": "dataforseo/keywords-data-bing-search-volume-history",
"input": {
"location_code": 2840,
"language_code": "en",
"keywords": [
"10 minute timer"
]
}
}Price and billing
- Price
- Usage based
- Model
- Usage based
- Detail
- Billed at the cost the provider reports for the call, never above $100. Your agent sees the maximum before running.
- The provider’s price, 0% markup.
- One prepaid balance for every provider; your agent sees the price before it runs.
- Pay for measured usage; unused reservations are released.