Skip to main content
Glama

ReviewTactic — Google Review Checker

Check negative reviews against Google policy

check_negative_reviews
Read-only

Read-only. Reads the public negative Google reviews of one business, compares them with Google review policies and returns counts, the policy categories that matched and up to 5 short excerpts of flagged reviews. It only reads public data: nothing is posted, reported, changed or removed on Google, and nobody is contacted. Pass place_id with place_name (from find_business), or a Google Maps link. Reading a business for the first time can take up to a minute; if the status is pending, call again with the same input to get the result. The result is an automated first check, not a guarantee that Google will remove a review.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_negative_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
maps_urlNoA Google Maps link to the business, instead of place_id and place_name.
place_idNoGoogle place_id from find_business. Send together with place_name.
place_nameNoBusiness name, sent together with place_id.

Output Schema

NameRequiredDescriptionDefault
cachedNo
statusYes
messageNo
place_idNo
learn_moreNo
place_nameNo
weak_countNo
flagged_countNo
total_reviewsNo
negative_countNo
flagged_reviewsNo
flagged_categoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and destructiveHint, but the description still adds substantial non-obvious behavior: first-time reads can take up to a minute, results may come back pending and require a re-call with identical input, no one is contacted, and the output is an automated first check rather than a guarantee of removal. That latency/polling/disclaimer detail is exactly the kind of context annotations cannot carry.

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?

It is front-loaded with the read-only guarantee and the core action, and the operational caveats (latency, pending retry, disclaimer) come after the essentials. There is mild redundancy between 'Read-only' and the later 'nothing is posted, reported, changed or removed' sentence, but each sentence still carries distinct practical information.

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?

For a tool with an output schema, three optional parameters and full schema coverage, the description covers everything an agent needs to call it correctly: input alternatives, a required pairing convention, first-call latency, the pending-state retry path, and an expectation-setting caveat about what the result means. Nothing material is missing.

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 documents that maps_url is an alternative to place_id plus place_name and that place_id must be sent with place_name. The description repeats that pairing and adds the useful provenance hint that place_id comes from find_business, but contributes no new format or constraint detail beyond the schema. 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?

The description opens with a specific verb and resource chain — reads public negative reviews, compares them against Google review policies, returns counts, matched policy categories and up to 5 excerpts. It also scopes what is explicitly out of scope (nothing posted, reported or removed), which separates it from a reporting/removal sibling like email_removal_report.

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?

It gives clear invocation context: pass place_id with place_name sourced from find_business, or alternatively a Google Maps link. It also gives retry guidance (if status is pending, call again with the same input). It does not explicitly state when to prefer this over check_local_rank or email_removal_report, so it stops short of full when-to-use/when-not-to-use coverage.

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.