Skip to main content
Glama

SEO Rank Fixer

New and lost links

backlink_changes
Read-onlyIdempotent

The links one site gained and lost in the last 7 or 30 days, grouped by linking site, lost first: the linking pages, the site's pages they point to, how many links remain from each site, the stored Authority score where known, and the next step for each list. From Bing Webmaster Tools refreshes and Search Console link exports already stored; asks nothing.

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

Input Schema

NameRequiredDescriptionDefault
daysNoThe period in days: 7 or 30 (default 30).
siteIdYesA site id from list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world behavior; the description adds real context beyond that — the data provenance (BWT refreshes and Search Console exports) and the fact that the call 'asks nothing' (no live fetch). It also discloses the return shape per group: linking pages, target pages, remaining link counts, stored Authority score, and a 'next step' per list.

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?

Purpose and window are front-loaded, then the grouped output contents are enumerated after a colon. Dense but every clause carries information; the single run-on sentence is the only structural weakness.

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 usefully carries the return shape and provenance, and annotations cover the safety profile. It is nearly complete for a two-parameter read tool; only the vague 'next step for each list' is left unexplained.

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 coverage is 100%, with the days parameter already constrained to 7 or 30 and defaulted, and siteId documented as coming from list_sites. The description only restates the 7/30-day window and adds no syntax or format detail beyond the schema, so the baseline 3 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?

States a specific verb-and-resource pair: links a site gained and lost over 7 or 30 days, grouped by linking site, lost first. The external-link framing ('linking pages', 'links remain from each site') implicitly distinguishes it from internal_links, but no sibling is named explicitly.

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?

Usage is implied by the 7/30-day window and by 'From Bing Webmaster Tools refreshes and Search Console link exports already stored; asks nothing', which signals it reads cached data rather than triggering a crawl. There is no explicit when-to-use versus when-not guidance and no alternative tool is referenced.

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.