Skip to main content
Glama

SEO and Keyword Data API

Backlink anchor texts (up to 100)

backlink_anchors
Read-onlyIdempotent

Anchor texts of the links to a domain, most used first: each anchor's backlinks, referring domains and main domains, nofollow domains and first seen, up to 100 rows per $0.048 call, from a web link index. Use when checking anchor-text distribution or over-optimisation. 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": "backlink_anchors"
  }
}

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?

Goes well beyond the readOnly/openWorld/idempotent annotations: it discloses billing on empty results, free 400s for bad input, no charge on data-source failure, the exact price, and the x402 USDC-on-Base payment passed via _meta["x402/payment"]. That is precisely the operational context an agent needs before spending money on a call.

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 the result shape, then usage, then cost/error behavior — a sensible order for an agent. There is mild redundancy: "up to 100 rows per $0.048 call" is restated later 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?

For a two-parameter, no-output-schema tool, the description covers return contents, ordering, row cap, cost, empty-result behavior, error charging, and the payment mechanism. There is no pagination to explain since the cap is 100 rows, so nothing an agent needs to call it correctly is missing.

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 both parameters are already documented (limit 1-100 default 20, target domain normalization rules). The description only echoes "up to 100 rows" and adds no syntax or edge-case meaning beyond the schema, which is the expected baseline when the schema does the work.

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?

"Anchor texts of the links to a domain, most used first" gives a specific resource plus ordering, and enumerates the row fields (backlinks, referring domains, nofollow domains, first seen). It stops short of naming which sibling to prefer (e.g. backlinks_list or referring_domains), and the phrase "referring domains" in the column list could momentarily blur with the sibling tool of that name.

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 checking anchor-text distribution or over-optimisation" gives a concrete decision context that maps well to a real SEO task. It does not state when-not to use it or point to a competing anchor/backlink tool, so the agent must infer the boundary from sibling names alone.

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.