Skip to main content
Glama

get_referring_domains

Read-only

The domains linking to a client's site, from the workspace's STORED DataForSEO answer (no new request, no charge), each with DataForSEO Rank, backlinks, first seen by DataForSEO, lost date, spam score, follow state and whether AI engines cited the domain in this client's own measured answers (citedByAI: answers of answersTotal in the window). Filters work on the rows that were pulled (rows of totalAtDataForSeo). Reads the stored answer of the asked status only (live links by default, lost links with status "lost"): lost links are never shown as current, and the result names its status. With no stored answer it says so; run_link_lookup buys one.

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": {
      "clientId": "<clientId>"
    },
    "name": "get_referring_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows returned, default 50.
domainNoDomain to read. Default: the client's own.
followNoOnly domains whose links are all follow, all nofollow, or mixed.
statusNoWhich stored answer to read: live links (default) or lost links. They are different lookups; the result says which it is.
minRankNoOnly domains with DataForSEO Rank at least this.
clientIdYesClient id (from list_clients).
aiCitedOnlyNoOnly domains AI engines cited in this client's answers.
firstSeenFromNoOnly domains first seen by DataForSEO on or after this day (YYYY-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnly/destructive annotations, the description discloses the cost profile (no new request, no charge), the degraded case (with no stored answer it says so), and the important filtering caveat that filters act on the rows pulled rather than the total at DataForSEO. It also warns that lost links are never surfaced as current and that the result names its own status, which prevents a real misreading of the data.

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?

It is front-loaded with the resource and source, and nearly every clause carries information the agent needs. The single dense paragraph with stacked parentheticals ("citedByAI: answers of answersTotal in the window", "rows of totalAtDataForSeo") reads as run-on and would scan better as short sentences.

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?

For an eight-parameter tool with no output schema, the description doubles as return-value documentation by enumerating the row fields (Rank, backlinks, first seen, lost date, spam score, follow state, AI citation). It covers the live/lost duality and the empty-answer case; only ordering and pagination behavior for limit are left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: it explains what citedByAI measures (answers of answersTotal in the window), that aiCitedOnly is scoped to this client's own measured answers, and that minRank/firstSeenFrom are applied against the pulled row set. Only the domain and limit parameters receive no extra narrative 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?

The description states a specific resource (referring domains linking to a client's site) and a specific source (the workspace's STORED DataForSEO answer), which an agent can act on immediately. It names run_link_lookup as the buying alternative, but does not distinguish itself from other link siblings such as get_link_overview, get_linked_pages, or get_link_anchors, so the differentiation is only partial.

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?

It gives explicit operating conditions: use the default live status for current links, pass status="lost" for lost links, and the fact that it only reads a stored answer while run_link_lookup buys one provides a clear alternative path. What is missing is any guidance on choosing this over the other link-report tools in the sibling set.

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.

Resources