Skip to main content
Glama
AgentSEO MCP Server

AgentSEO MCP Server

AgentSEO Backlinks Referring Domains

agentseo_backlinks_referring_domains
Destructive

Analyze a target’s referring domains to filter and sort by authority, spam score, live or lost status, and broken links, supporting quality review, outreach, and lost-link recovery.

Instructions

Analyze referring domains and classify authority, lost-domain recovery, broken-link repair, quality review, and outreach patterns. Uses AgentSEO credits; repeating the call can create new charged work.

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": "agentseo_backlinks_referring_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
syncNoRequest a bounded wait for completion when true. The API can still return a pending job; retain its job ID and poll agentseo_job_status instead of repeating this charged call. False returns a queued job without waiting. Type: Boolean. Default: true.
limitNoMaximum number of referring-domain records to return. Type: Safe integer. Minimum: 1. Maximum: 100. Default: 25.
offsetNoZero-based result offset measured in rows; use with limit for pagination. Type: Safe integer. Minimum: 0. Maximum: 20000. Default: 0.
targetYesTarget domain, subdomain or absolute page URL to analyze; use a hostname or URL, not a business name. Type: String. Minimum: 1 characters. Required.
sort_byNoMetric used to order returned results; choose one of this tool’s accepted enum values. Type: String. Accepted values: "rank", "backlinks", "referring_pages", "spam_score", "broken_backlinks", "first_seen", "lost_date". Default: "rank".rank
min_rankNoMinimum provider backlink authority score, not a Google search position; use the supported score scale and stated input bounds. Type: Safe integer. Minimum: 0. Maximum: 1000. Optional; no client default.
rank_scaleNoRequested provider authority-score scale: one_hundred is 0-100; one_thousand is 0-1000. Individual filter input bounds still apply. Type: String. Accepted values: "one_hundred", "one_thousand". Default: "one_hundred".one_hundred
dofollow_onlyNoRestrict results to followed backlinks when true; false does not apply that filter. Type: Boolean. Default: false.
domain_filterNoText filter to match the referring domain. Type: String. Minimum: 1 characters. Maximum: 120 characters. Optional; no client default.
min_backlinksNoMinimum backlink count for an aggregate record to be included. Type: Safe integer. Minimum: 1. Maximum: 10000000. Optional; no client default.
include_subdomainsNoInclude links or ranking data for subdomains of the target when true. Type: Boolean. Default: true.
internal_list_limitNoMaximum embedded sample rows per aggregate record; this does not cap the aggregate backlink totals. Type: Safe integer. Minimum: 1. Maximum: 100. Default: 10.
min_referring_pagesNoMinimum count of referring pages for a referring-domain record to be included. Type: Safe integer. Minimum: 1. Maximum: 10000000. Optional; no client default.
backlinks_status_typeNoBacklink lifecycle filter: live links only, lost links only, or all supported links. Type: String. Accepted values: "live", "all", "lost". Default: "live".live
include_indirect_linksNoInclude backlinks that reach the target through supported indirect/redirect link relationships when true. Type: Boolean. Default: true.
exclude_internal_backlinksNoExclude links originating within the target’s own site when true. Type: Boolean. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changedv0.1.5
    • addedInput schema / properties / backlinks_status_type / description
      Added value: +"Backlink lifecycle filter: live links only, lost links only, or all supported links. Type: String. Accepted values: \"live\", \"all\", \"lost\". Default: \"live\"."
    • addedInput schema / properties / dofollow_only / description
      Added value: +"Restrict results to followed backlinks when true; false does not apply that filter. Type: Boolean. Default: false."
    • addedInput schema / properties / domain_filter / description
      Added value: +"Text filter to match the referring domain. Type: String. Minimum: 1 characters. Maximum: 120 characters. Optional; no client default."
    • addedInput schema / properties / exclude_internal_backlinks / description
      Added value: +"Exclude links originating within the target’s own site when true. Type: Boolean. Default: true."
    • addedInput schema / properties / include_indirect_links / description
      Added value: +"Include backlinks that reach the target through supported indirect/redirect link relationships when true. Type: Boolean. Default: true."
    • addedInput schema / properties / include_subdomains / description
      Added value: +"Include links or ranking data for subdomains of the target when true. Type: Boolean. Default: true."
    • addedInput schema / properties / internal_list_limit / description
      Added value: +"Maximum embedded sample rows per aggregate record; this does not cap the aggregate backlink totals. Type: Safe integer. Minimum: 1. Maximum: 100. Default: 10."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of referring-domain records to return. Type: Safe integer. Minimum: 1. Maximum: 100. Default: 25."
    • addedInput schema / properties / min_backlinks / description
      Added value: +"Minimum backlink count for an aggregate record to be included. Type: Safe integer. Minimum: 1. Maximum: 10000000. Optional; no client default."
    • addedInput schema / properties / min_rank / description
      Added value: +"Minimum provider backlink authority score, not a Google search position; use the supported score scale and stated input bounds. Type: Safe integer. Minimum: 0. Maximum: 1000. Optional; no client default."
    • addedInput schema / properties / min_referring_pages / description
      Added value: +"Minimum count of referring pages for a referring-domain record to be included. Type: Safe integer. Minimum: 1. Maximum: 10000000. Optional; no client default."
    • addedInput schema / properties / offset / description
      Added value: +"Zero-based result offset measured in rows; use with limit for pagination. Type: Safe integer. Minimum: 0. Maximum: 20000. Default: 0."
    • addedInput schema / properties / rank_scale / description
      Added value: +"Requested provider authority-score scale: one_hundred is 0-100; one_thousand is 0-1000. Individual filter input bounds still apply. Type: String. Accepted values: \"one_hundred\", \"one_thousand\". Default: \"one_hundred\"."
    • addedInput schema / properties / sort_by / description
      Added value: +"Metric used to order returned results; choose one of this tool’s accepted enum values. Type: String. Accepted values: \"rank\", \"backlinks\", \"referring_pages\", \"spam_score\", \"broken_backlinks\", \"first_seen\", \"lost_date\". Default: \"rank\"."
    • addedInput schema / properties / sync / description
      Added value: +"Request a bounded wait for completion when true. The API can still return a pending job; retain its job ID and poll agentseo_job_status instead of repeating this charged call. False returns a queued job without waiting. Type: Boolean. Default: true."
    • addedInput schema / properties / target / description
      Added value: +"Target domain, subdomain or absolute page URL to analyze; use a hostname or URL, not a business name. Type: String. Minimum: 1 characters. Required."
  2. First observedv0.1.4

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is largely covered. The description still adds meaningful context beyond them: it discloses that calls consume AgentSEO credits and that repeating a call may spawn new charged work, which tells an agent to prefer polling (as the sync param's schema text also advises). It does not describe output shape, but that is not required for this dimension.

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?

Two sentences, front-loaded with the operation and immediately followed by the credit/repeat-call warning. The mid-sentence theme list ('lost-domain recovery, broken-link repair, quality review, outreach patterns') is somewhat promotional and could be trimmed, but nothing is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter, non-idempotent, credit-consuming analysis tool with no output schema, the description covers cost behavior but says nothing about what a referring-domain record contains or how aggregates relate to the embedded sample rows controlled by internal_list_limit. The rich schema compensates for most parameter gaps, leaving the definition adequate but not fully self-explanatory.

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% across all 16 parameters, including enums, bounds, defaults and an explicit note to poll agentseo_job_status instead of re-invoking. The description contributes no parameter-level meaning beyond that, so the 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?

The description gives a specific verb+resource ('Analyze referring domains'), so an agent knows the general operation. However, it never distinguishes this tool from the many backlink siblings (agentseo_backlinks_list, agentseo_backlinks_domain_pages, agentseo_backlinks_summary), and the trailing list of themes (authority, lost-domain recovery, broken-link repair, outreach) describes use cases rather than what the tool actually returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use / when-not-to-use guidance and no named alternative. The only guidance-like statement is a cost warning that repeating the call creates new charged work, which is a behavioral caution rather than a selection rule. Given eight backlink-oriented siblings, the absence of routing guidance is a real gap.

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