Skip to main content
Glama
Sign In
MCP DataForSEO Server

MCP DataForSEO Server

by kevinmaqueda
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_referring_domains

List domains linking to any target, showing authority, backlink count, dofollow ratio, and first-seen date. Use this data to analyze link equity and identify outreach opportunities.

Instructions

Get detailed list of domains linking to a target. Returns domain authority, backlink counts, dofollow ratio, and dates.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of referring domains (default 100)
domainYesThe domain to analyze
order_byNoSort order (default: rank)rank

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the return data (domain authority, backlink counts, dofollow ratio, dates) which is helpful. However, it does not disclose behavioral aspects such as whether it's a read-only operation, any rate limits, pagination behavior, or authentication requirements. More context would be expected.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that effectively communicates the tool's purpose and key return fields. No unnecessary words or repetition.

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 a simple tool with only 3 well-documented parameters and no output schema, the description covers the essential return values. It doesn't mention any caveats or limitations, but the tool is straightforward. The description is adequate for this complexity level.

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 baseline is 3. The description does not add significant meaning beyond what the schema already provides for parameters like 'domain', 'limit', and 'order_by'. It only reinforces that the tool analyzes 'a target' domain.

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?

The description states exactly what the tool does: 'Get detailed list of domains linking to a target.' It uses a specific verb and resource, and clearly distinguishes from sibling tools like get_anchor_texts (anchor texts) and get_backlinks_summary (summary).

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?

The context is clear: this is for analyzing domains that link to a target. However, it does not explicitly mention when to use it over alternatives like get_backlinks_summary or get_new_lost_backlinks, nor does it provide exclusions. Lacks explicit alternative guidance.

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

Deploy Server

Other Tools