Skip to main content
Glama

Google Business Profile & Local SEO Checker

Draft a competitor spam report

draft_spam_report
Read-onlyIdempotent

Drafts a factual report about a competitor's Google listing that breaks the guidelines (keyword-stuffed name, fake address, duplicates, fake reviews, closed business), with where to send it and the evidence to attach. Only drafts the text. Nothing is submitted.

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": {
      "competitor_name": "<competitor_name>",
      "issue": "<issue>"
    },
    "name": "draft_spam_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueYesType of violation
evidenceNoOptional: links or facts that prove it
competitor_nameYesListing name as shown on Google

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: the output is text only and nothing is submitted, plus it discloses that the report includes where to send it and what evidence to attach. It stops short of describing length, format, or how evidence is used, keeping it at a 4.

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?

Two sentences, front-loaded with the core action and scope, with the critical constraint ("Nothing is submitted") placed last for emphasis. No filler or redundant restatement of the 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?

With no output schema, the description carries the burden of describing the return, and it does so adequately by naming the report's contents (violation summary, submission destination, evidence to attach). A brief note on report length or format would make it fully complete, but nothing essential for correct invocation 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. The description earns above baseline by mapping the enumerated violation types to the `issue` enum and clarifying that `evidence` is the supporting material to attach, giving the agent a clearer sense of what to supply than the terse schema descriptions alone.

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 ("Drafts") and resource ("a factual report about a competitor's Google listing") and enumerates the exact violation categories covered (keyword-stuffed name, fake address, duplicates, fake reviews, closed business). This clearly separates it from sibling audit/check tools, which diagnose rather than produce a report artifact.

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

Usage Guidelines3/5

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

The description scopes the tool well by saying "Only drafts the text. Nothing is submitted," which tells the agent this is a preparation step, not a filing action. However, it never states when to reach for this versus siblings like audit_gbp_profile or suspension_triage, so the agent must infer the routing.

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