SEO Performance MCP

AI-citation losses per URL

posts_cite_loss

Read-onlyIdempotent

Find which LLMs stopped citing a URL, see the original query, last-seen date, and any replacement URL to diagnose lost citations.

Instructions

Return the list of LLMs that previously cited this URL but no longer do, with the prior query and last-seen date. Optionally includes the URL that replaced ours.

Requires a configured citation-intelligence MCP endpoint (CITATION_INTELLIGENCE_URL). Otherwise returns an empty list.

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": {
      "url": "<url>"
    },
    "name": "posts_cite_loss"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Canonical URL of the post.

Output Schema

Name	Required	Description	Default
`url`	Yes
`active`	Yes
`losses`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.1.2Oct 2, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/open-world, so the safety profile is covered. The description adds genuinely non-structured behavioral context: the dependency on a configured citation-intelligence endpoint and the degraded-mode result (empty list) when it is absent, plus the shape of what is returned.

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 tight sentences: the return content is front-loaded, and the operational caveat follows immediately. No filler or repetition of the name or 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?

For a one-parameter, read-only tool with an output schema and rich annotations, the description covers purpose, degraded-mode behavior, and return content. The only missing element is routing guidance against sibling tools, which is a minor gap.

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?

Schema description coverage is 100% for the single url parameter, so the schema already carries the meaning. The description adds nothing about the URL's expected format or canonicalization beyond what the schema states. Baseline 3 is appropriate.

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 (Return) and a precisely defined resource (LLMs that previously cited this URL but no longer do), plus the payload fields (prior query, last-seen date). This 'citation loss' concept is clearly distinct from sibling tools like posts_decay_curve, posts_snapshot, and posts_verdict.

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 discloses a usage prerequisite (a configured CITATION_INTELLIGENCE_URL, otherwise an empty list), which is useful context. However, it never says when to prefer this tool over alternatives such as posts_decay_curve or posts_verdict, and no exclusions are given. Implied usage only.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server