Skip to main content
Glama

Google Business Profile & Local SEO Checker

Check a review reply

check_review_reply
Read-onlyIdempotent

Checks an owner's reply to a Google review before posting it: privacy leaks (addresses, invoice numbers, health details), offers to change a review, argumentative tone, generic one-liners, length. Gives advice suited to the star rating.

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": {
      "reply": "<reply>"
    },
    "name": "check_review_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
replyYesThe drafted reply
starsNoStar rating of the review (1-5)
review_textNoOptional: the review being replied to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds real value by disclosing the specific checks performed and that advice is tailored to the star rating, though it does not describe the shape or severity of the returned advice.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; each clause names a distinct check. It is dense and slightly list-like, but nothing is wasted.

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 read-only, three-parameter checker with no output schema, the description covers what is inspected and how input affects output. The main remaining gap is the format of the returned advice, which an agent would have to discover by calling.

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?

Schema coverage is 100%, so the baseline is 3. The description goes beyond the schema by explaining that 'stars' drives the tailoring of advice and that the review text is contextual input, adding meaning the schema alone does not convey.

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 ('Checks an owner's reply to a Google review') and enumerates the exact dimensions checked: privacy leaks, review-change offers, tone, generic one-liners, length. This is clearly distinguishable from siblings like check_review_request or check_gbp_post.

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?

'before posting it' gives a clear timing/context for use, which is genuinely useful guidance. However, it never names an alternative or states when not to use it (e.g., versus check_review_request for incoming reviews), so routing is left to inference.

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.