post_dataforseo_serp_google_organic_liveLive SERP provides real-time data on top search engine results for the specified keyword, search engine, and location. This endpoint will supply a complete overview of featured snippets and other extra elements of SERPs.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / properties / body / items / properties / calculate_rectangles / descriptionPrevious value: -"Calculate pixel rankings for SERP elements"New value: +"calcualte pixel rankings for SERP elements in advanced results optional field pixel ranking refers to the distance between the result snippet and top left corner of the screen; Visit Help Center to learn more>> by default, the parameter is set to false; Note: you will be charged extra $0.002 for using this parameter"Input schema / properties / body / items / properties / depth / descriptionPrevious value: -"Parsing depth, default 100, max 700"New value: +"parsing depth optional field number of results in SERP default value: 10 max value: 200 Your account will be billed per each SERP containing up to 10 results; Setting depth above 10 may result in additional charges if the search engine returns more than 10 results; The cost can be calculated on the Pricing page."Input schema / properties / body / items / properties / device / descriptionPrevious value: -"Device type: desktop or mobile"New value: +"device type optional field return results for a specific device type can take the values:desktop, mobile default value: desktop"Input schema / properties / body / items / properties / keyword / descriptionPrevious value: -"Keyword to search for"New value: +"keyword required field you can specify up to 700 characters in the keyword field all %## will be decoded (plus character ‘+’ will be decoded to a space character) if you need to use the “%” character for your keyword, please specify it as “%25”; if you need to use the “+” character for your keyword, please specify it as “%2B”; if this field contains such parameters as ‘allinanchor:’, ‘allintext:’, ‘allintitle:’, ‘allinurl:’, ‘cache:’, ‘define:’, ‘definition:’, ‘filetype:’, ‘id:’, ‘inanchor:’, ‘info:’, ‘intext:’, ‘intitle:’, ‘inurl:’, ‘link:’, ‘site:’, the charge per task will be multiplied by 5 learn more about rules and limitations of keyword and keywords fields in DataForSEO APIs in this Help Center article"Input schema / properties / body / items / properties / language_code / descriptionPrevious value: -"Search engine language code"New value: +"search engine language code optional field if you 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 engine with their language_code by making a separate request to the https://api.dataforseo.com/v3/serp/google/languages example: en"Input schema / properties / body / items / properties / language_name / descriptionPrevious value: -"Full name of search engine language"New value: +"full name of search engine language optional field if you 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 engine with their language_name by making a separate request to the https://api.dataforseo.com/v3/serp/google/languages example: English"Input schema / properties / body / items / properties / location_code / descriptionPrevious value: -"Search engine location code"New value: +"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 the search engines with their location_code by making a separate request to the https://api.dataforseo.com/v3/serp/google/locations example: 2840"Input schema / properties / body / items / properties / location_coordinate / descriptionPrevious value: -"GPS coordinates of a location"New value: +"GPS coordinates of a location optional field if you 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 \"latitude,longitude,radius\" format the maximum number of decimal digits for \"latitude\" and \"longitude\": 7 the minimum value for \"radius\": 199 (mm) the maximum value for \"radius\": 199999 (mm) example: 53.476225,-2.243572,200"Input schema / properties / body / items / properties / location_name / descriptionPrevious value: -"Full name of search engine location"New value: +"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 locations of the search engine with their location_name by making a separate request to the https://api.dataforseo.com/v3/serp/google/locations example: London,England,United Kingdom"Input schema / properties / body / items / properties / max_crawl_pages / descriptionPrevious value: -"Page crawl limit, max 100"New value: +"page crawl limit optional field number of search results pages to crawl max value: 100 Note: you will be charged for each page crawled (10 organic results per page); learn more about pricing on our Pricing page; Note#2: the max_crawl_pages and depth parameters complement each other; learn more at our help center"Input schema / properties / body / items / properties / os / descriptionPrevious value: -"Device operating system"New value: +"device operating system optional field if you specify desktop in the device field, choose from the following values: windows, macos default value: windows if you specify mobile in the device field, choose from the following values: android, ios default value: android"Input schema / properties / body / items / properties / tag / descriptionPrevious value: -"User-defined task identifier"New value: +"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"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=true, openWorldHint=true, idempotentHint=false), so the description does not need to restate it. The description adds only modest extra context — that results are 'real-time' and include featured snippets and other SERP extras — while omitting the highest-impact trait, per-task billing and surcharges (depth>10, special operators), which is the real reason this POST is not read-only. No contradiction with the annotations, but a notable gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no padding, and the core capability is front-loaded in the first sentence. It is efficient, though the second sentence is largely decorative detail about featured snippets rather than information that changes how the tool is called.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a billed, non-idempotent POST with a nested body array, ten optional fields and cost multipliers, the description says nothing about credit consumption, batch usage or required inputs. An output schema exists, so return values need not be explained, but the pre-call operational context an agent needs is absent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Reported schema description coverage for the sole top-level parameter (body) is 0%, so the description is expected to compensate; it names only keyword, search engine and location, adding no syntax, format or default information. The nested item schema is detailed in its own right, which keeps this above a 1, but the description leaves required fields, batch-array semantics and billing-affecting options entirely to the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a concrete verb+resource: retrieving real-time top organic Google search results for a given keyword, engine and location, plus the extra SERP elements (featured snippets) it returns. An agent can distinguish it from siblings like bing_organic_live, google_news_live or google_maps_live from the organic/featured-snippet framing, though the description never explicitly says 'Google' or contrasts with those siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit when-to-use or when-not-to-use guidance and no alternative named, despite a large sibling set (news, maps, local finder, AI mode, Bing, YouTube). Usage is only implicit in 'real-time data', leaving the agent to infer that this is for live Google organic rankings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.