Skip to main content
Glama

SEO Rank Fixer

Brand mentions

brand_mentions
Read-onlyIdempotent

Pages on other sites that mention one site's brand (found by a web search for its brand terms, the site's own domain left out), whether each page links to the site, the user's progress (new, asked, won, ignored) and, for pages that do not link yet, a short draft note asking the owner for a link that the user edits and sends themselves. From stored checks only; asks nothing new and contacts no one.

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": {
      "siteId": "<siteId>"
    },
    "name": "brand_mentions"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesA site id from list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description nonetheless adds real context beyond them: results come only from stored checks, the site's own domain is excluded from the search, and the draft note is not sent by the tool but edited and sent by the user, which preempts a false assumption that this tool contacts anyone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence front-loads the core resource and then layers the exclusion rule, the returned fields, and the no-side-effects caveat. Every clause carries information, though the run-on structure makes it harder to scan than a few short bullets would.

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?

With one fully documented parameter, rich annotations, and no output schema, the description carries the remaining burden of describing what comes back, and it does: link status, progress state, and draft note. Nothing an agent needs in order to call it correctly is missing.

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?

There is a single parameter whose schema already fully documents it as a UUID taken from list_sites. The description adds nothing about siteId beyond what the schema provides, so the baseline of 3 for complete schema coverage applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (pages on other sites mentioning the site's brand) and enumerates the fields returned: link status, user progress states, and a draft outreach note. It also states the discovery method (a web search for brand terms with the site's own domain excluded), which distinguishes it from generic backlink tools, though it never names a sibling directly.

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?

"From stored checks only; asks nothing new and contacts no one" tells the agent this reads cached results and performs no outreach, which implies when-not to use it when fresh data is needed. However, it gives no explicit alternative to call instead (for example a scan or freshness-checking tool), so the routing guidance is only inferable.

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.