Skip to main content
Glama

SEO Rank Fixer

Site story

site_story
Read-onlyIdempotent

The whole picture of one site in one reply, for "show me my site" or "how is my site doing": headline numbers, clicks trend, a map of the site's sections, every opportunity by kind with the clicks it could win, a before/after Google result for the top title fix, a 3-month projection, and how the site does in Google, answer boxes and AI assistants. Comes with display guidance for charts and diagrams.

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": "site_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesA site id from list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds behavior beyond that: everything is delivered in a single reply (a single broad round-trip), it bundles derived artifacts such as a projection and a before/after SERP mock, and it ships display guidance for charts and diagrams. It stops short of stating response size, cost, or default time windows, which would matter for a report this broad.

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

Conciseness3/5

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

The scope statement is front-loaded well, but the body is one long run-on enumeration separated by commas, which is harder to scan than a short bulleted style list. Every listed artifact is relevant, yet the density hurts readability rather than adding noise.

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 must carry the return contract, and it does by naming each section the reply contains, including the chart display guidance. The main omission is framing around scope limits - default date range, whether the projection/opportunities depend on data volume, or expected latency for such a broad payload - which an agent would want before calling it casually.

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?

Only one parameter, and the schema documents it at 100% coverage including the 'from list_sites' provenance hint and UUID format. The description adds nothing about siteId or about what the wide scope of the report implies for that input. Baseline 3 applies because the schema already carries the semantics.

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 (one site) and a specific deliverable (a bundled report), then enumerates the sections: headline numbers, clicks trend, section map, opportunities, before/after SERP preview, 3-month projection, AI visibility. An agent can tell it is an aggregate 'everything at once' tool. It does not explicitly contrast itself with siblings like site_performance, opportunities or top_fixes, so the boundary between this and the narrower tools is left for the agent to infer.

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?

"for 'show me my site' or 'how is my site doing'" gives concrete trigger phrases that map to real user requests, which is stronger than generic guidance. There is no negative guidance, however: nothing says when to prefer the leaner siblings (site_performance, top_fixes) or that this is a heavier catch-all.

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.