Skip to main content
Glama

SEO and Keyword Data API

Backlink profile history (up to 24 months)

backlinks_history
Read-onlyIdempotent

Monthly history of a domain's backlink profile: rank (0-1000), backlinks, new and lost backlinks, referring domains, new and lost referring domains and main domains per month, for up to 24 months (from 2019 on; default the last 24 months) per $0.048 call, from a web link index. Use when tracking link growth or a lost-link drop over time. No history is an empty answer, which is still charged. Bad input is a free 400; a data source failure is not charged. Price: $0.048 per successful call, paid over x402 (USDC on Base); pass the payment in _meta["x402/payment"].

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": {
      "target": "<target>"
    },
    "name": "backlinks_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateToNoLast day, YYYY-MM-DD, after dateFrom and not after today (UTC). Default today.
targetYesA domain like example.com (subdomains allowed). A site-root URL such as https://www.example.com/ is reduced to the domain; a path or port is refused.
dateFromNoFirst day, YYYY-MM-DD, on or after 2019-01-01, at most 24 months before dateTo. Default 24 months before dateTo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • changedInput schema / properties / target / description
      Previous value: -"A bare domain like example.com (no scheme, path or port; subdomains allowed)."New value: +"A domain like example.com (subdomains allowed). A site-root URL such as https://www.example.com/ is reduced to the domain; a path or port is refused."
  3. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, it discloses billing behavior that annotations cannot convey: $0.048 per successful call, an empty history is still charged, bad input is a free 400, and data-source failure is not charged. It also explains the x402 payment mechanism and the _meta["x402/payment"] field, which is operationally essential for actually invoking the tool.

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?

Front-loads what the tool returns, then usage, then billing rules — a sensible ordering for an agent scanning for fit. It is dense but nearly every clause carries information; the only waste is the price being stated twice ('$0.048 per call' near the start and again as 'Price: $0.048 per successful call').

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 no output schema, the description compensates by listing the returned fields and the monthly granularity, and it covers the three things an agent needs before calling: validity rules, cost, and how to pay. Nothing material is missing for a three-parameter, read-only, paid endpoint.

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%, so dateFrom, dateTo and target are already fully documented in the schema, including the 2019-01-01 floor, 24-month cap and domain-vs-URL normalization. The description's 'up to 24 months, from 2019 on, default the last 24 months' restates those constraints rather than adding new meaning, so baseline 3 applies.

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 — 'Monthly history of a domain's backlink profile' — and enumerates the returned metrics (rank, backlinks, new/lost backlinks, referring domains, main domains). The word 'history' plus 'per month' cleanly separates it from snapshot siblings like backlinks_summary, backlinks_list and referring_domains without needing to name them.

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 an explicit use condition: 'Use when tracking link growth or a lost-link drop over time.' That is a clear usage context and implies the snapshot siblings are for point-in-time checks. It stops short of naming an alternative tool or stating when not to use it, so it is not 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.