Skip to main content
Glama

AgentSEO Backlinks Referring Domains

agentseo_backlinks_referring_domains
Destructive

Analyze referring domains and classify authority, lost-domain recovery, broken-link repair, quality review, and outreach patterns.

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
syncNo
limitNo
offsetNo
targetYes
sort_byNorank
min_rankNo
rank_scaleNoone_hundred
dofollow_onlyNo
domain_filterNo
min_backlinksNo
include_subdomainsNo
internal_list_limitNo
min_referring_pagesNo
backlinks_status_typeNolive
include_indirect_linksNo
exclude_internal_backlinksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior1/5

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

The description frames the tool purely as read-only analysis ('Analyze ... classify'), but the annotations declare readOnlyHint=false and destructiveHint=true. Nothing in the description warns of a destructive or mutating side effect, nor does it explain the 'sync' parameter's write behavior, pagination, or cost. This is a direct mismatch with the supplied annotations.

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

Conciseness3/5

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

The definition is a single front-loaded sentence with no filler, which is structurally sound. But the second half is a vague feature checklist whose terms are never explained, so the brevity comes partly at the cost of substance.

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

Completeness2/5

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

For a tool with 16 parameters, zero schema descriptions, no output schema, and a destructive annotation, the description is far too thin. It neither explains what is returned, how pagination works, nor what the destructive/sync behavior actually does to the target's data.

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

Parameters2/5

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

With 16 parameters at 0% schema description coverage, the description carries the full burden but provides almost nothing. The only faint mapping is thematic ('authority' ↔ min_rank/rank_scale, 'lost-domain' ↔ backlinks_status_type, 'broken-link repair' ↔ broken_backlinks sort); the other twelve parameters (limit, offset, domain_filter, dofollow_only, include_subdomains, exclude_internal_backlinks, internal_list_limit, etc.) get no clarification at all.

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 verb+resource pair 'Analyze referring domains' is specific and distinguishes this tool from sibling backlink tools such as agentseo_backlinks_anchors, agentseo_backlinks_list and agentseo_backlinks_summary. However, the trailing list ('classify authority, lost-domain recovery, broken-link repair, quality review, and outreach patterns') is marketing phrasing rather than a concrete description of the operation.

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?

The description never states when to use this tool versus the many sibling tools (backlinks_list, backlinks_competitors, backlinks_opportunity_finder) that also surface referring-domain data. There are no prerequisites, exclusions, or alternative-selection cues, leaving the agent to infer routing from the name 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.