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
itemsNo
statusYes
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the mutation risk is partly covered. The description adds genuinely new behavioral facts: exactly one real email is sent, and there is a hard limit of one send per address/business per day. It does not describe deliverability failures or what the recipient sees, so it stops short of 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 tight sentences lead with the action, then the gating condition, then the side-effect limits. Every sentence carries a distinct operational constraint and none repeats the schema.

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 an irreversible outbound-email tool with two params, full schema coverage and an output schema, the description supplies everything an agent needs before calling: prerequisite check, user-consent requirement, and per-day send limit. Return values are covered by the output schema, so nothing material is missing.

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, but the description adds provenance constraints the schema does not: the email must be user-typed in this conversation rather than inferred, and place_id must reference a business already checked. That extra semantic guardrail justifies a bump.

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 names a specific verb and resource (sends the written review-removal report) and pins its scope with two prerequisites: the business must already have been checked via check_negative_reviews, and the target is an email address. That distinguishes it immediately from the read-only siblings like check_local_rank and find_business.

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?

It gives an explicit when-to-call condition (only after the user has typed their own email address in this conversation) and names the gating sibling tool. There is no ambiguity about sequencing, which is critical for a tool that sends a real email.

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.