Skip to main content
Glama

SteadyScrape Local Leads

Review themes and rating trend

review_summary
Read-only

Analyses the recent reviews of 1-3 businesses (Google Maps, Trustpilot or Tripadvisor) and returns per business: a short summary, up to 8 complaint themes and 6 praise themes with mention counts, share and short example excerpts, suggested actions, rating distribution, monthly trend and owner reply rate. No reviewer names. Billed per review analysed plus one report per business. Can take 1-3 minutes; may return a run_id.

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": "review_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
sort_byNoReview order (default newest). lowest_rating works for Google only.
targetsYes1-3 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_to_analyzeNoRecent reviews to analyse per business (default 50; Trustpilot max 200).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond annotations, the description discloses privacy behavior (no reviewer names), cost structure (billed per review plus one report per business), latency (1-3 minutes), and asynchronous behavior (may return a run_id). These are exactly the operational traits an agent needs before invoking a costly analysis 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?

The description front-loads the purpose, then efficiently covers outputs, privacy, billing, and latency in a compact sequence. Every sentence adds useful information and there is no boilerplate or repetition.

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?

For a complex, potentially asynchronous and billable analysis tool with no output schema, the description is nearly complete: it explains returned content, privacy, cost, and latency. The main gap is that it mentions a possible run_id without explaining that get_results should be used to retrieve it.

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 description coverage is 100%, so the schema already explains targets, sort order, language, location, and review count. The description only restates the 1-3 business scope and does not add parameter-level meaning beyond what the schema provides.

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?

The description gives a specific verb (analyses), resource (recent reviews of 1-3 businesses), supported sources, and exact output categories. This makes it clearly distinct from business_reviews by focusing on summaries and themes rather than raw review retrieval.

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

Usage Guidelines3/5

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

Usage is implied by the stated output — summaries, themes, trends — rather than explicitly contrasted with siblings like business_reviews or get_results. The schema mentions find_local_businesses for place_id, but the description itself gives no explicit when-to-use or when-not-to-use guidance.

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