Skip to main content
Glama

Google Business Profile & Local SEO Checker

Read the review data a website publishes

read_site_reviews
Read-onlyIdempotent

Pulls the rating, review count and individual reviews a business publishes on its own site through schema.org aggregateRating and Review markup. Use it to get a review count and rating without asking the user, then feed them to benchmark_business. Reports when a site publishes no review data at all, which is a finding in itself.

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": {
      "website": "<website>"
    },
    "name": "read_site_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteYesThe business's website

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is covered structurally. The description adds genuinely new behavioral information: the data source is embedded schema.org markup, and a site with no review data returns a 'no review data' finding rather than an error — an important edge case an agent must plan for.

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?

Three short sentences: what it extracts, when to use it and what to do next, then the null-result behavior. The method and the outcome are front-loaded with no redundant restatement of the name or title.

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 single-parameter read tool with rich annotations and no output schema, the description covers source, output fields, downstream use, and the empty-result case. It does not address failure modes such as unreachable sites or markup present but malformed, which leaves a small gap.

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

Parameters4/5

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

Only one parameter exists and the schema documents it at 100% coverage, so the baseline is 4. The description adds useful framing by establishing that the website is the source of the markup being parsed, though it offers no format or normalization guidance for the URL.

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 ('Pulls') and a precise resource ('rating, review count and individual reviews a business publishes on its own site'), and names the exact extraction mechanism (schema.org aggregateRating and Review markup). This makes it clearly distinguishable from siblings like check_review_reply or find_google_profile, which concern different review surfaces.

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?

Gives explicit usage context ('get a review count and rating without asking the user') and names the downstream consumer, benchmark_business, which routes the agent's next step. It stops short of stating when not to use it — e.g., when the business has a Google profile but no site markup — so it is strong but not fully exhaustive.

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