Skip to main content
Glama

ReviewTactic — Google Review Checker

Email the review removal report

email_removal_report
Destructive

Sends the written review-removal report for a business that was already checked with check_negative_reviews to an email address. Call only after the user has typed their own email address in this conversation. Sends one real email; it can send at most once per address and business per day.

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": {
      "place_id": "<place_id>",
      "email": "<email>"
    },
    "name": "email_removal_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesThe email address the user typed in this conversation.
place_idYesplace_id of a business already checked with check_negative_reviews.

Output Schema

NameRequiredDescriptionDefault
sentNo
statusYes
messageNo
more_countedNo
cases_written_upNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, openWorldHint=true), the description discloses that a real email is sent and that throughput is throttled to at most once per address and business per day. That rate-limit fact is not derivable from any structured field and is the most decision-relevant behavior here. It stops short of describing failure behavior when the daily limit is hit or what happens to an invalid address, which keeps it from a 5.

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 sentences, front-loaded with what the tool does before the preconditions and the rate limit. Every clause carries decision-relevant information with no filler or restated title.

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?

An output schema exists, so return-value explanation is unnecessary, and the annotations already declare the safety profile. For a two-parameter side-effecting send tool, the description covers purpose, prerequisite, and throttle, leaving nothing an agent needs in order to call it correctly.

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% and the two parameters already carry descriptions mirroring the intent ('the email address the user typed in this conversation', 'place_id of a business already checked with check_negative_reviews'). The description restates those constraints rather than adding format or validation detail, so baseline 3 applies.

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 ('sends the written review-removal report') plus scope ('for a business that was already checked with check_negative_reviews') and destination ('to an email address'). An agent can distinguish this from check_negative_reviews or check_local_rank without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit precondition for invocation: 'Call only after the user has typed their own email address in this conversation,' and names the upstream tool that must have run first. It also implies the negative case (no user-typed address, no call) rather than leaving the agent to infer it.

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.