Skip to main content
Glama

Visibility Genies

Save several competitors

save_competitors

Add up to 50 competitors in one call, each a website, a name, or both, with an optional note, as the Add several box does. Websites are normalized, the project's own site is left out, and a website already saved is updated in place. Rivals with a website are tracked while Tracking has room for ten; the rest are saved under Suggested. Returns how many are tracking, suggested and updated. Confirm the list with the user first. 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>",
      "competitors": "<competitors>"
    },
    "name": "save_competitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes
competitorsYes

Output Schema

NameRequiredDescriptionDefault
metaNo
resultYes

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?

Annotations only declare the safety profile (not read-only, not destructive, closed-world), so the description carries the real burden and does well: it discloses normalization, exclusion of the project's own site, in-place update of already-saved websites, the ten-slot tracking limit with overflow to Suggested, and that no credits are used. The upsert and quota behavior are exactly the traits an agent could not infer otherwise.

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?

Dense but front-loaded: the batch scope and item shape come first, then normalization/upsert behavior, then quota routing, then the confirmation instruction. Every clause carries operational information with no filler.

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 two-parameter batch write with an output schema, the description covers input shape, side effects, quota behavior, and even summarizes the return counts. Nothing an agent needs to invoke it correctly 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 0%, so the description must compensate, and it does: it explains that each competitor may be a website, a name, or both, that a note is optional, and that the cap is 50. It leaves projectId and the domain/name field mapping implicit, which is a minor 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?

States a specific verb and resource ('Add up to 50 competitors in one call') and implicitly distinguishes itself from the singular save_competitor by the batch scope and the 50-item cap. An agent can tell exactly what this does without opening the schema.

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?

Gives a concrete procedural instruction ('Confirm the list with the user first') and explains the tracking-vs-suggested routing rule that determines outcomes. It does not explicitly name save_competitor as the single-item alternative, which keeps it from a 5.

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