Skip to main content
Glama
AgentSEO MCP Server

AgentSEO MCP Server

AgentSEO Backlinks List

agentseo_backlinks_list
Destructive

Retrieve a bounded list of actionable backlinks and classify each for protection, repair, reclaim, quality review, or outreach reference.

Instructions

Return a bounded list of actionable backlinks and classify each one for protection, repair, reclaim, quality review, or outreach reference. 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_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoBacklink grouping strategy: raw rows, at most one row per referring domain, or at most one row per anchor. Type: String. Accepted values: "as_is", "one_per_domain", "one_per_anchor". Default: "one_per_domain".one_per_domain
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 backlink rows to return for this page of results. 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", "page_rank", "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: 100. 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
broken_onlyNoRestrict results to backlinks associated with broken target pages when true. Type: Boolean. Default: false.
dofollow_onlyNoRestrict results to followed backlinks when true; false does not apply that filter. Type: Boolean. Default: false.
intersection_modeNoWhether matches must cover every supplied target (all) or a supported subset (partial). Type: String. Accepted values: "all", "partial". Default: "partial".partial
include_subdomainsNoInclude links or ranking data for subdomains of the target when true. Type: Boolean. Default: true.
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. Changed15 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 / broken_only / description
      Added value: +"Restrict results to backlinks associated with broken target pages when true. Type: Boolean. Default: false."
    • 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 / intersection_mode / description
      Added value: +"Whether matches must cover every supplied target (all) or a supported subset (partial). Type: String. Accepted values: \"all\", \"partial\". Default: \"partial\"."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of backlink rows to return for this page of results. Type: Safe integer. Minimum: 1. Maximum: 100. Default: 25."
    • 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: 100. Optional; no client default."
    • addedInput schema / properties / mode / description
      Added value: +"Backlink grouping strategy: raw rows, at most one row per referring domain, or at most one row per anchor. Type: String. Accepted values: \"as_is\", \"one_per_domain\", \"one_per_anchor\". Default: \"one_per_domain\"."
    • 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\", \"page_rank\", \"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 declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, openWorldHint=true, and the description usefully adds the cost model ("Uses AgentSEO credits") and the concrete consequence of non-idempotency ("repeating the call can create new charged work"). It does not reconcile the destructive hint with what looks like a listing operation — nothing states what is destroyed or side-effected — so the behavioral picture is incomplete rather than wrong.

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 dense sentences with no filler, and the core purpose is front-loaded ahead of the cost warning. Both sentences earn their place, though the second sentence could be slightly tighter given that the sync parameter already explains the charged-repeat behavior.

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 15-parameter, charged, destructive-flagged tool with no output schema, the description says just enough to call it safely but not enough to call it well. It names the output classifications, which substitutes for an output schema, yet it omits pagination/job-follow-up context (only present in the schema) and any differentiation from sibling backlink tools.

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 15 parameters, including enum meanings, defaults, and bounds, so the schema already carries the parameter burden. The description contributes no additional meaning about any specific parameter (mode, sync, rank_scale, backlinks_status_type are all left entirely to the schema), which matches the baseline 3 for high coverage.

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 ("return a bounded list of actionable backlinks") plus what is done with each row (classification into protection/repair/reclaim/quality review/outreach reference). That is far more concrete than a bare name restatement, but it never distinguishes itself from the many sibling backlink tools (agentseo_backlinks_summary, _referring_domains, _anchors, _opportunity_finder), so an agent has no basis to pick this one.

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 gives no when-to-use context and no alternatives; it does not say how this list differs from the summary, referring-domains, or anchors tools. The only guidance offered is a caution against repeating the call, which is a warning rather than selection criteria.

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