post_dataforseo_business_google_gmb_info_liveBusiness Data API provides results containing information about specific business entity from Google. The provided results are specific to the selected location (see the List of Locations) and language (see the List of Languages) settings.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / properties / body / items / properties / keyword / descriptionPrevious value: -"*keyword* **required field** the keyword you specify should indicate the name of the local establishment you can specify **up to 700 characters** in the `keyword` filed **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”; this field can also be used to pass the following parameters: `cid` – a unique, google-defined id of the business entity; `place_id` – an identifier of the business entity in Google Maps; `spp` – a unique identifier of local services featured in the `local_pack` element of Google SERP example: `cid:194604053573767737` `place_id:GhIJQWDl0CIeQUARxks3icF8U8A` `spp:CgsvZy8xdGN4cWRraBoUChIJPZDrEzLsZIgRoNrpodC5P30` learn more about the `cid` and `place_id` identifiers in [this help center article](https://dataforseo.com/help-center/what-is-cid-place-id-feature-id) learn more about rules and limitations of `keyword` and `keywords` fields in DataForSEO APIs in this [Help Center article](https://dataforseo.com/help-center/rules-and-limitations-of-keyword-and-keywords-fields-in-dataforseo-apis)"New value: +"keyword required field the keyword you specify should indicate the name of the local establishment you can specify up to 700 characters in the keyword filed 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”; this field can also be used to pass the following parameters: cid - a unique, google-defined id of the business entity; place_id - an identifier of the business entity in Google Maps; example: cid:194604053573767737 place_id:GhIJQWDl0CIeQUARxks3icF8U8A learn more about the cid and place_id identifiers in [this help center article](https://dataforseo.com/help-center/what-is-cid-place-id-feature-id) learn more about rules and limitations of keyword and keywords fields in DataForSEO APIs in this [Help Center article](https://dataforseo.com/help-center/rules-and-limitations-of-keyword-and-keywords-fields-in-dataforseo-apis)"Input schema / properties / body / items / properties / language_code / descriptionPrevious 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 with their `language_code` by making a separate request to `https://api.dataforseo.com/v3/business_data/google/languages` example: `en`"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 with their language_code_by making a separate request to https://api.dataforseo.com/v3/business_data/google/languages example: enn"Input schema / properties / body / items / properties / location_code / descriptionPrevious 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 with `location_code` by making a separate request to the `https://api.dataforseo.com/v3/business_data/google/locations` example: `2840`"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 with location_code by making a separate request to the https://api.dataforseo.com/v3/business_data/google/locations example: 2840n"Input schema / properties / body / items / properties / location_coordinate / descriptionPrevious 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,radius”* format the maximum number of decimal digits for *“latitude”* and *“longitude”*: 7 the minimum value for *“radius”*: 199.9 (mm) the maximum value for *“radius”*: 199999 (mm) example: `53.476225,-2.243572,200`"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,radius\" format the maximum number of decimal digits for \"latitude\" and \"longitude\": 7 the minimum value for \"radius\": 199.9 (mm) the maximum value for \"radius\": 199999 (mm) example: 53.476225,-2.243572,200n"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, and idempotentHint=false, indicating a non-read-only, potentially destructive, external-interaction operation. The description does not mention that this creates a live task, that it may have side effects, or that it is non-idempotent. It also fails to explain what 'live' means or what happens to previous data, leaving a significant gap for a mutation tool. This is not a contradiction, but the description adds no behavioral context beyond the 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?
The description consists of two sentences that are somewhat concise, but they are generic and not front-loaded with actionable information. The first sentence restates part of the tool name/title, and the second adds minor detail about location/language. There is no wasted text, but the content is insufficient.
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?
Given the complexity (nested array parameter with multiple required fields), the presence of an output schema (which the description doesn't need to cover), and the annotations indicating a non-read-only, destructive operation, the description is highly incomplete. It omits any mention of the task creation aspect, parameter requirements, or behavioral implications. The agent would struggle to use this tool correctly.
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 schema description coverage is 0% (per context signals), yet the description provides no information about parameters. The single parameter 'body' is an array of objects with complex nested requirements (keyword, location/language constraints, etc.), none of which are explained in the description. The description completely fails to compensate for the lack of schema documentation, making it impossible for an agent to know how to structure the request.
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 states the tool provides business entity information from Google, specific to location and language, which gives a rough idea of the resource. However, it doesn't specify that this tool creates a live task (as implied by the tool name and 'Setting' in the title), or distinguish it from siblings like post_dataforseo_business_google_hotel_info_live or post_dataforseo_business_listings_search_live. The verb is vague and the resource is only implied.
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 indication of when to use this tool versus alternatives. The description provides no context about prerequisites, differences from similar tools (e.g., hotel_info_live, hotel_searches_live, qa_live), or any exclusions. The agent is left to infer usage entirely.
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.