Skip to main content
Glama

Visibility Genies

Remove a competitor

remove_competitor
Destructive

Remove a saved competitor after the user requests it. Use status ignored via save_competitor to suppress a suggestion instead. Uses no credits.

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": {
      "projectId": "<projectId>",
      "id": "<id>"
    },
    "name": "remove_competitor"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
projectIdYes
expectedRevisionNo

Output Schema

NameRequiredDescriptionDefault
metaNo
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature needs no restating; the description adds genuinely new context in "Uses no credits" and the user-request gating. It does not address reversibility/undo, nor how expectedRevision conflicts are handled, which matter for an irreversible removal.

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 short sentences, front-loaded with the action and followed by the alternative and cost note. Every clause carries information; no filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Return values are covered by the output schema and destructiveness by annotations, and the usage routing is strong. The remaining gap is parameter-level guidance for a destructive mutation with three undocumented fields, especially what expectedRevision guards against.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, including a non-obvious expectedRevision, and the description mentions none of them. An agent gets no meaning for projectId, id, or the concurrency token beyond the bare field names, so the description fails to compensate for the coverage gap.

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?

"Remove a saved competitor" is a specific verb plus resource, and the description immediately frames it against save_competitor's suppression mechanism, so an agent can distinguish deleting a saved competitor from merely ignoring a suggestion. No sibling ambiguity remains for the core action.

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 trigger ("after the user requests it") and an explicit when-not with the alternative named: use status ignored via save_competitor to suppress a suggestion instead. This covers when, when-not, and the routing alternative without 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.

Resources