AgentSEO MCP Server

AgentSEO Backlinks Domain Pages

agentseo_backlinks_domain_pages

Destructive

Analyze backlink-bearing pages to classify linkable assets, broken-link pages, lost links, refresh candidates, and quality risks for SEO targeting.

Instructions

Analyze backlink-bearing pages and classify linkable assets, broken backlink pages, lost links, refresh candidates, and quality risks. 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_domain_pages"
  }
}

Input Schema

Name	Required	Description	Default
`sync`	No	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.
`limit`	No	Maximum number of linked target-page records to return. Type: Safe integer. Minimum: 1. Maximum: 100. Default: 25.
`offset`	No	Zero-based result offset measured in rows; use with limit for pagination. Type: Safe integer. Minimum: 0. Maximum: 20000. Default: 0.
`target`	Yes	Target domain, subdomain or absolute page URL to analyze; use a hostname or URL, not a business name. Type: String. Minimum: 1 characters. Required.
`sort_by`	No	Metric used to order returned results; choose one of this tool’s accepted enum values. Type: String. Accepted values: "backlinks", "referring_domains", "rank", "spam_score", "broken_backlinks", "first_visited", "words_count", "external_links". Default: "backlinks".	backlinks
`min_words`	No	Minimum reported page word count for inclusion. Type: Safe integer. Minimum: 1. Maximum: 1000000. Optional; no client default.
`rank_scale`	No	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".	one_hundred
`page_filter`	No	Text filter to match the page URL. Type: String. Minimum: 1 characters. Maximum: 160 characters. Optional; no client default.
`status_code`	No	HTTP response status code, for example 200 or 404; not an application job status. Type: Safe integer. Minimum: 100. Maximum: 599. Optional; no client default.
`title_filter`	No	Text filter to match the reported page title. Type: String. Minimum: 1 characters. Maximum: 160 characters. Optional; no client default.
`dofollow_only`	No	Restrict results to followed backlinks when true; false does not apply that filter. Type: Boolean. Default: false.
`min_backlinks`	No	Minimum backlink count for an aggregate record to be included. Type: Safe integer. Minimum: 1. Maximum: 10000000. Optional; no client default.
`include_subdomains`	No	Include links or ranking data for subdomains of the target when true. Type: Boolean. Default: true.
`internal_list_limit`	No	Maximum embedded sample rows per aggregate record; this does not cap the aggregate backlink totals. Type: Safe integer. Minimum: 1. Maximum: 100. Default: 10.
`backlinks_status_type`	No	Backlink lifecycle filter: live links only, lost links only, or all supported links. Type: String. Accepted values: "live", "all", "lost". Default: "live".	live
`min_referring_domains`	No	Minimum count of distinct referring domains for a record to be included. Type: Safe integer. Minimum: 1. Maximum: 10000000. Optional; no client default.
`exclude_internal_backlinks`	No	Exclude links originating within the target’s own site when true. Type: Boolean. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedv0.1.5Nov 5, 2026

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 / 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_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 linked target-page 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_referring_domains / description

Added value: +"Minimum count of distinct referring domains for a record to be included. Type: Safe integer. Minimum: 1. Maximum: 10000000. Optional; no client default."

addedInput schema / properties / min_words / description

Added value: +"Minimum reported page word count for inclusion. Type: Safe integer. Minimum: 1. Maximum: 1000000. 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 / page_filter / description

Added value: +"Text filter to match the page URL. Type: String. Minimum: 1 characters. Maximum: 160 characters. Optional; no client default."

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: \"backlinks\", \"referring_domains\", \"rank\", \"spam_score\", \"broken_backlinks\", \"first_visited\", \"words_count\", \"external_links\". Default: \"backlinks\"."

addedInput schema / properties / status_code / description

Added value: +"HTTP response status code, for example 200 or 404; not an application job status. Type: Safe integer. Minimum: 100. Maximum: 599. Optional; no client default."

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."

addedInput schema / properties / title_filter / description

Added value: +"Text filter to match the reported page title. Type: String. Minimum: 1 characters. Maximum: 160 characters. Optional; no client default."

First observedv0.1.4Nov 4, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare non-read-only, non-idempotent, destructive, and open-world behavior. The description usefully adds that AgentSEO credits are consumed and that a repeated call can incur new charges, which reinforces the non-idempotent hint. However, it does not explain what a charged analysis actually does to state or what the destructive hint means in practice, so added value is moderate.

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?

Two short sentences with the analytical scope front-loaded and the cost caution second; nothing is wasted. It is efficiently sized for a definition whose parameter detail lives in the schema.

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?

With 17 parameters, no output schema, and a destructive/charged annotation profile, the description is minimally adequate but omits what the returned page classifications look like and the conditions under which a pending job should be polled. The schema covers inputs well, but an agent would still need inference to know the result shape and sync/pending workflow.

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 all 17 parameters, including enum values and defaults for sort_by, rank_scale, and backlinks_status_type, are already documented in the schema. The description adds no parameter-level meaning beyond that, which is acceptable at the baseline when the schema does the heavy lifting.

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?

States a specific verb and resource: analyzing backlink-bearing pages and classifying them into linkable assets, broken pages, lost links, refresh candidates, and quality risks. That distinguishes it reasonably from anchors/referring-domain/direct-list siblings, though it never explicitly names those siblings or contrasts their scopes.

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 only usage guidance is the cost warning that repeating the call can create new charged work. There is no indication of when to prefer this tool over agentseo_backlinks_list, agentseo_backlinks_referring_domains, or agentseo_backlinks_page_intersection, nor any prerequisites or exclusions.

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

Deploy Server