Skip to main content
Glama
Sign In

SEO and Keyword Data API

by com.duoleads.keywords
OverviewDiscussionsAdmin

Backlinks list (up to 100)

backlinks_list
Read-onlyIdempotent

Backlinks of a domain, strongest first: linking page URL and domain, target URL, anchor text, link type, dofollow, first and last seen, and the rank (0-1000) of the linking domain and page, up to 100 rows per $0.048 call, optionally dofollow only, from a web link index. Use when auditing who links to a site. Anchors are the linking pages' own text. 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": "backlinks_list"
  }
}

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.
dofollowOnlyNoOnly dofollow links. Default false.

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

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

Goes well beyond the readOnly/openWorld/idempotent annotations: it discloses the 100-row ceiling, the $0.048 per-call price, that an empty result is still billed, that malformed input returns a free 400 while a source failure is uncharged, and the x402/USDC-on-Base payment mechanism via _meta['x402/payment']. It also clarifies ordering ('strongest first') and what anchor text represents, which an agent could otherwise misread.

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?

Single dense paragraph that front-loads the resource, then returned fields, then usage, then pricing/error economics in a logical order. It is information-rich with little waste, losing a point only because returned-field enumeration and billing caveats are packed into one long, comma-chained sentence that is harder to scan than discrete lines.

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 still names every returned field, states ordering and row cap, and covers cost, free-400 behavior, uncharged source failures, and the payment handshake. For a paid, open-world read tool this is enough for an agent to call it correctly and anticipate both results and billing.

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%, so the schema already documents target, limit (1-100, default 20), and dofollowOnly (default false). The description only restates 'up to 100 rows' and 'optionally dofollow only' without adding format or edge-case meaning beyond the schema, so 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 concrete resource ('Backlinks of a domain') and enumerates the returned fields (linking page URL/domain, target URL, anchor, link type, dofollow, first/last seen, rank). It is clear what the tool delivers, though it never distinguishes itself from close siblings like backlinks_summary, backlinks_history, referring_domains, or backlink_anchors.

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?

Provides one usage cue, 'Use when auditing who links to a site,' which implies the right context. It gives no when-not guidance and no route to the overlapping siblings (e.g., when to prefer referring_domains for aggregated counts or backlinks_history for trend data), so selection between them is left to inference.

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

All SEO and Keyword Data API toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources