post_dataforseo_serp_google_ai_mode_liveGoogle AI Mode SERP API provides search results from the AI Mode feature of Google Search.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / properties / body / items / properties / browser_screen_height / descriptionPrevious value: -"Custom browser screen height"New value: +"browser screen height optional field you can set a custom browser screen height to calculate pixel rankings for a particular device; can be specified within the following range: 240-9999; by default, the parameter is set to: 1080 for desktop; 640 for mobile on android; 812 for mobile on iOS; Note: to use this parameter, set calculate_rectangles to true"Input schema / properties / body / items / properties / browser_screen_resolution_ratio / descriptionPrevious value: -"Screen resolution ratio for rectangle calculations"New value: +"browser screen resolution ratio optional field you can set a custom browser screen resolution ratio to calculate pixel rankings for a particular device; can be specified within the following range: 0.5-3; by default, the parameter is set to: 1 for desktop; 3 for mobile on android; 3 for mobile on iOS; Note: to use this parameter, set calculate_rectangles to true"Input schema / properties / body / items / properties / browser_screen_width / descriptionPrevious value: -"Custom browser screen width"New value: +"browser screen width optional field you can set a custom browser screen width to calculate pixel rankings for a particular device; can be specified within the following range: 240-9999; by default, the parameter is set to: 1920 for desktop; 360 for mobile on android; 375 for mobile on iOS; Note: to use this parameter, set calculate_rectangles to true"Input schema / properties / body / items / properties / calculate_rectangles / descriptionPrevious value: -"Enable pixel ranking calculations for elements in SERP"New value: +"calculate 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: if set to true, the charge per task will be multiplied by 2"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; you can specify up to 700 characters"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” 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; required if language_name is not specified"New value: +"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 engine with their language_code by making a separate request to the https://api.dataforseo.com/v3/serp/google/ai_mode/languages"Input schema / properties / body / items / properties / language_name / descriptionPrevious value: -"Full name of search engine language; required if language_code is not specified"New value: +"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 engine with their language_name by making a separate request to the https://api.dataforseo.com/v3/serp/google/ai_mode/languages;"Input schema / properties / body / items / properties / location_code / descriptionPrevious value: -"Search engine location code; required if location_name or location_coordinate is not specified"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 Note: check Google Search Help for the list of countries where AI Mode is currently available"Input schema / properties / body / items / properties / location_coordinate / descriptionPrevious value: -"GPS coordinates of a location; required if location_name or location_code is not specified"New value: +"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 \"latitude,longitude,zoom\" format if \"zoom\" is not specified, 9z will be applied as a default value the maximum number of decimal digits for \"latitude\" and \"longitude\": 7 the minimum value for \"zoom\": 4z the maximum value for \"zoom\": 18z example: 52.6178549,-155.352142,18z"Input schema / properties / body / items / properties / location_name / descriptionPrevious value: -"Full name of search engine location; required if location_code or location_coordinate is not specified"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 Note: check Google Search Help for the list of countries where AI Mode is currently available"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the profile (readOnlyHint=false, destructiveHint=true, openWorldHint=true, idempotentHint=false), so the bar is lower, but the description adds nothing behavioral: no mention that this is a live (billable, open-world) request, no auth or rate-limit notes, no note on whether the call mutates state or is merely an expensive read. No contradiction with annotations.
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?
One front-loaded sentence with no filler, so nothing wastes space. However it is under-specified rather than well-scoped; brevity here reflects missing content rather than tight editing.
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?
An output schema exists, so return values need not be explained, but for a live search endpoint with an opaque body parameter and an open-world/destructive annotation profile, the description supplies neither usage context nor behavioral detail. It is inadequate for an agent to invoke confidently beyond guessing from siblings.
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?
The single parameter is an opaque 'body' array and schema description coverage is reported at 0% for the top level, so the description must compensate. It says nothing about the required keyword, the location/language fields, or the optional screen/rectangle parameters, leaving the semantics entirely to the nested 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?
The description names a specific resource (AI Mode search results from Google Search) but is essentially a restatement of the title 'Live Google AI Mode SERP'. It never distinguishes this endpoint from close siblings like post_dataforseo_serp_ai_summary or post_dataforseo_serp_google_organic_live, so an agent cannot route between them from the description alone.
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 when-to-use, when-not-to-use, or alternative-selection guidance. With many overlapping SERP siblings in the list, the absence of any routing hint is a real gap.
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.