AIsa Business Listings & Reviews

Setting Live Google My Business Questions and Answers Tasks

post_dataforseo_business_google_qa_live

Destructive

This endpoint will provide you with a detailed overview of questions and answers associated with a specific business entity listed on Google My Business. By submitting a request to this endpoint, you can access comprehensive data on the inquiries and responses related to a particular business, including the full text of the questions and answers, as well as metadata such as timestamps, user information. The provided results are specific to the selected location (see the List of Locations) and language (see the List of Languages) settings. Your account will be billed for every 20 questions, the maximum number of answers returned for each question is 5.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`body`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 28, 2026

changedInput schema / properties / body / items / properties / keyword / description

Previous 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)"

changedInput schema / properties / body / items / properties / language_code / description

Previous 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"

changedInput schema / properties / body / items / properties / location_code / description

Previous 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"

changedInput schema / properties / body / items / properties / location_coordinate / description

Previous 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"

First observedSep 15, 2026

TDQS

C2.4/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations mark the tool as not read-only, destructive, open-world, and non-idempotent, suggesting a mutating operation. The description instead frames it as purely data retrieval, which contradicts the destructive/ write hints (see annotation contradiction flag). Additionally, it does not explain the billing model fully or the destructiveness implied by annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately concise but front-loads less critical information. Some sentences, like the billing and answer limit details, are useful, but the overall structure lacks a clear logical flow from purpose to usage to parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema, so return values need not be explained. However, the description does not cover key aspects like the expected input structure (a body array of task objects), authentication needs, or the discrepancy between stated retrieval behavior and the destructive annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning no parameter descriptions are provided in the schema. The tool description fails to compensate, offering no details about required fields, the body array structure, or how to specify a business entity beyond a vague reference to 'location' and 'language' settings.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear purpose: retrieving questions and answers for a Google My Business entity, with explicit mention of full text and metadata. This distinguishes it from reviews siblings (which fetch reviews) but does not explicitly name those siblings for contrast.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives is provided. The description does not mention the sibling review endpoints or explain the differences between live submission and retrieval modes present in other sibling names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AIsa Business Listings & Reviews tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?