Skip to main content
Glama
Sign In

Scrappa

by co.scrappa
OverviewDiscussionsAdmin

Read Google Maps reviews of a place

google_maps_get_reviews
Read-onlyIdempotent

Read public Google Maps reviews of one place. Needs the business_id from google_maps_search_places. Returns per review: star rating, date, review text, review language and the owner reply. By default only reviews with text are returned. Reviewer names and profiles are never returned. Reads public data only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "business_id": "<business_id>"
    },
    "name": "google_maps_get_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoOrder of the reviews. Default: newest.
limitNoNumber of reviews to return, 1 to 20. Default: 10.
languageNoTwo-letter language code, e.g. "en" or "de". Default: en.
business_idYesThe business_id of the place, from google_maps_search_places, e.g. "0x47a851c655f20989:0x26bbfb4e84674c63".
include_rating_onlyNoAlso return reviews that only have a star rating and no text. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_rating_only
      Added value: +{
+  "description": "Also return reviews that only have a star rating and no text. Default: false.",
+  "type": "boolean"
+}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare safety (readOnly, idempotent, openWorld); the description adds real behavioral context beyond them — the per-review return fields, the default text-only filtering behavior, and a hard privacy constraint ('reviewer names and profiles are never returned'). It also scopes the data to public sources, which matters for an open-world tool.

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

Conciseness5/5

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

Five short sentences, front-loaded with the purpose, then prerequisite, then return shape, then behavioral caveats. Nothing is padded and every sentence carries information an agent can act on.

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

Completeness5/5

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

With no output schema, the description compensates by enumerating the return fields per review and stating the exclusion (reviewer identities). Combined with the fully documented params and safety annotations, an agent has everything needed to call this correctly.

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?

Schema coverage is 100% and every parameter is documented inline with defaults, enums, and ranges, so the description adds little. Its mention of default text-only filtering overlaps with the include_rating_only schema description. Baseline 3 is appropriate.

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

Purpose5/5

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

States a specific verb and resource ('Read public Google Maps reviews of one place') and is clearly distinct from google_maps_search_places, which it names as the source of the required identifier. An agent can immediately tell what it does and what it does not do.

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

Usage Guidelines4/5

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

Explicitly states the prerequisite ('Needs the business_id from google_maps_search_places'), which chains the sibling tools correctly, and notes the default text-only filter with an escape hatch hint. It stops short of naming explicit when-not-to-use cases, but the usage context is unambiguous.

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

All Scrappa 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