Skip to main content
Glama

SEO and Keyword Data API

Referring domains (up to 100)

referring_domains
Read-onlyIdempotent

Domains linking to a domain, strongest first: each referring domain's rank (0-1000), backlinks and linking pages to the target, nofollow and broken links, first seen and spam score, up to 100 rows per $0.048 call, from a web link index. Use when sizing or comparing a site's link sources. No links 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": "referring_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return, 1-100. Default 20.
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.

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.1/5.0
Behavior5/5

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

Annotations only cover read-only/idempotent/open-world; the description adds genuinely new behavior: per-call price, that an empty result is still charged, that a bad input is a free 400, that a data-source failure is not charged, and the x402/USDC-on-Base payment mechanism passed in _meta. That is exactly the cost and failure semantics an agent needs before calling a paid 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-loaded with purpose and output fields, then cost and failure semantics. Slightly redundant: the $0.048 price appears both in the first sentence and again in the closing 'Price:' clause, which could be consolidated.

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?

No output schema exists, and the description compensates by listing the returned fields. It also covers pricing, payment, and error-charging rules, so an agent has everything needed to invoke it correctly and predict the cost.

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 both parameters are already documented with formats and the 1-100 bound. The description's 'up to 100 rows per $0.048 call' only restates the limit ceiling and ties it to cost, adding little semantic detail beyond the schema.

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?

Opens with a specific verb+resource: 'Domains linking to a domain, strongest first', then enumerates the returned metrics (rank 0-1000, backlinks, linking pages, nofollow/broken, first seen, spam score). This clearly separates it from siblings like backlinks_list or backlinks_summary, though 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use when sizing or comparing a site's link sources' gives a concrete use context. There are no exclusions or explicit alternative tools (e.g. when to prefer backlinks_list for individual links), so it stops short of full routing guidance.

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.