Skip to main content
Glama
Sign In

AIsa Business Listings & Reviews

by one.aisa
OverviewDiscussionsAdmin

Get Business Data Google Extended Reviews Results by id

get_dataforseo_business_google_extended_reviews_fetch
Read-onlyIdempotent

The returned results are specific to the indicated local establishment name, search engine, location and language parameters. We emulate set location and search engine with the highest accuracy so that the results you receive will match the actual search results for the specified parameters at the time of task setting. You can always check the returned results accessing the check_url in the Incognito mode to make sure the received data is entirely relevant. Note that user preferences, search history, and other personalized search factors are ignored by our system and thus would not be reflected in the returned results.

Published reference price: $0 USD per successful request. Account-specific pricing and final settlement may differ.

Input Schema

NameRequiredDescriptionDefault
idYes<em>task identifier</em><br><strong>unique task identifier in our system in the <a href="https://en.wikipedia.org/wiki/Universally_unique_identifier">UUID</a> format</strong><br>you will be able to use it within <strong>30 days</strong> to request the results of the task at any time

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"task identifier unique task identifier in our system in the UUID format you will be able to use it within 30 days to request the results of the task at any time"New value: +"<em>task identifier</em><br><strong>unique task identifier in our system in the <a href=\"https://en.wikipedia.org/wiki/Universally_unique_identifier\">UUID</a> format</strong><br>you will be able to use it within <strong>30 days</strong> to request the results of the task at any time"
    • addedInput schema / properties / id / example
      Added value: +"00000000-0000-0000-0000-000000000000"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  2. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"<em>task identifier</em><br><strong>unique task identifier in our system in the <a href=\"https://en.wikipedia.org/wiki/Universally_unique_identifier\">UUID</a> format</strong><br>you will be able to use it within <strong>30 days</strong> to request the results of the task at any time"New value: +"task identifier unique task identifier in our system in the UUID format you will be able to use it within 30 days to request the results of the task at any time"
    • removedInput schema / properties / id / example
      Removed value: -"00000000-0000-0000-0000-000000000000"
    • removedOutput schema / x-fastmcp-wrap-result
      Removed value: -true
  3. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"task identifier unique task identifier in our system in the UUID format you will be able to use it within 30 days to request the results of the task at any time"New value: +"<em>task identifier</em><br><strong>unique task identifier in our system in the <a href=\"https://en.wikipedia.org/wiki/Universally_unique_identifier\">UUID</a> format</strong><br>you will be able to use it within <strong>30 days</strong> to request the results of the task at any time"
    • addedInput schema / properties / id / example
      Added value: +"00000000-0000-0000-0000-000000000000"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  4. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"DataForSEO task ID."New value: +"task identifier unique task identifier in our system in the UUID format you will be able to use it within 30 days to request the results of the task at any time"
  5. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive reads, so the safety profile is covered. The description adds genuinely useful context beyond them: results reflect emulated location/search-engine settings, personalization is ignored, and check_url lets you verify relevance. It says nothing about rate limits, error states, or what happens for expired tasks.

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 text is front-loaded with output-fidelity caveats rather than the tool's action, and the Incognito-mode verification sentence is tangential padding. It is not bloated, but the opening sentence does not earn its position.

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

Completeness3/5

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 needn't be explained, yet most of the description is spent on result characteristics anyway. The critical missing pieces — that this is the fetch half of a submit/fetch pair and that the id must come from a prior submit — are absent.

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

Parameters3/5

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

There is a single parameter with 100% schema coverage, and the schema already documents the UUID format and 30-day validity window. The description adds no meaning beyond the schema, so the baseline of 3 applies.

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

Purpose3/5

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

The description never states the retrieval action (fetch task results by id); it opens with 'The returned results are specific to...' and describes output characteristics instead of what the tool does. The verb+resource is only recoverable from the name/title. No sibling differentiation from the other *_fetch tools is provided.

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?

There is no guidance on when to call this versus post_dataforseo_business_google_extended_reviews_submit (which presumably creates the task) or the other review-source fetch tools. Nothing explains that a task id from a prior submit is required, nor any timing/preconditions.

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 toolsInspect
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