Skip to main content
Glama

SteadyScrape Local Leads

Recent reviews of businesses

business_reviews
Read-only

Recent reviews of 1-5 businesses from Google Maps, Trustpilot or Tripadvisor: rating, title, text (first 600 characters), date, language and the owner's reply, plus rating stats and a monthly trend per business. Reviewer names, profiles and photos are never returned. Billed per review returned plus a run start fee.

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": {
      "targets": "<targets>"
    },
    "name": "business_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
sort_byNoReview order (default newest). lowest_rating works for Google only.
targetsYes1-5 businesses, one per item: a Google Maps place URL, place_id:<id> (from find_local_businesses), "Business name, street, city", a Trustpilot URL or trustpilot:<domain>, or a Tripadvisor review page URL.
languageNoGoogle review language code (default en), e.g. es, fr, de.
google_locationNoCountry or city used to find a Google business given by name (default "United States"), e.g. "London,England,United Kingdom".
reviews_per_businessNoReviews per business (default 20). businesses x reviews_per_business must be <= 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations by disclosing data truncation (first 600 characters of text), privacy exclusions (reviewer names, profiles and photos are never returned) and the commercial model (billed per review plus a run start fee). The cost-per-record warning is exactly the kind of pre-call context an agent needs.

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?

Two sentences, front-loaded with scope and sources, then the return contents, then the negative space (what is not returned) and billing. No filler sentences.

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

Completeness4/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 carries the return-value burden and does so thoroughly, including what is omitted. Remaining gaps are minor: no mention of pagination, deduplication across sources, or the failure mode when a target cannot be resolved.

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%, so parameter documentation is already handled. The description reinforces the 1-5 business cap and the 600-character text limit, but adds no syntax or format detail beyond what the schema descriptions state. Baseline 3 applies.

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?

Names a specific verb+resource (recent reviews) plus the sources (Google Maps, Trustpilot, Tripadvisor), the batch size (1-5 businesses) and the exact fields returned. An agent can tell it is a raw-review puller rather than a summarizer, though it never names the sibling review_summary to sharpen that distinction.

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 explicit when-to-use or when-not guidance and no mention of alternatives. The agent must infer from the field list that this is for retrieving raw review text versus a summary, and only the targets schema hints at find_local_businesses as a prerequisite.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources