AgentSEO MCP Server

AgentSEO Backlinks Summary

agentseo_backlinks_summary

Destructive

Summarize backlink authority, referring domains, spam risk, broken backlinks, and next SEO actions for a domain, subdomain, or URL to prioritize link-building work.

Instructions

Summarize backlink authority, referring domains, spam risk, broken backlinks, and next SEO actions for a domain, subdomain, or URL. 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_summary"
  }
}

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.
`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.
`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
`dofollow_only`	No	Restrict results to followed backlinks when true; false does not apply that filter. Type: Boolean. Default: false.
`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
`include_indirect_links`	No	Include backlinks that reach the target through supported indirect/redirect link relationships when true. Type: Boolean. Default: true.
`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.

Changed9 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_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 / 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 / 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."

First observedv0.1.4Nov 4, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already flag non-readOnly, non-idempotent, destructive and open-world, so the key risk is known; the description adds the crucial cost semantic — AgentSEO credits are consumed and repeating the call can spawn new charged work — which is not derivable from annotations or schema. It does not disclose latency or that a pending job may be returned, though the schema's sync parameter covers polling. No contradiction with 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?

Two short sentences with no filler, but the ordering is slightly off: the credit-cost warning — the highest-value behavioral fact — trails after the output list and gets no emphasis. It is concise but not maximally front-loaded on the decision-critical information.

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?

With no output schema, the description effectively stands in for it by enumerating the report's contents, which is enough for an agent to know what it gets back. Nine parameters, all schema-documented, and annotations present, so the remaining burden is small; the only real gap is that pending-job behavior is only visible via the schema's sync field rather than the description.

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% and every parameter is documented there, including the charged-call/poll guidance for sync, so baseline 3 applies. The description only reinforces the target parameter's accepted forms (hostname or URL, not a business name) and adds nothing about rank_scale, lifecycle filters, or sampling limits.

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 (summarize) and enumerates the concrete outputs: authority, referring domains, spam risk, broken backlinks, next SEO actions, plus the accepted target types (domain, subdomain, URL). It does not name or contrast with the closest siblings (agentseo_backlinks_list, agentseo_backlinks_referring_domains), so an agent must infer that this is the aggregate/overview variant.

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

Usage Guidelines3/5

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

The word 'summarize' implies an overview use case versus the detailed list tools, and the second sentence gives a real usage constraint (repeat calls create new charged work, implying cache/reuse the job ID). However, there is no explicit when-to-use statement, no named alternative, and no guidance on choosing between this and the several other backlink siblings.

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

Deploy Server