Skip to main content
Glama
AgentSEO MCP Server

AgentSEO MCP Server

AgentSEO Backlinks Competitors

agentseo_backlinks_competitors
Destructive

Identify backlink-profile competitors for a domain or page, ranked by authority and link overlap, to prioritize link-gap research and outreach targets.

Instructions

Discover backlink-profile competitors and prioritize overlap, authority, and link-gap research actions. 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_competitors"
  }
}

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 backlink competitor 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", "intersections", "opportunity". Default: "opportunity".opportunity
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.
main_domainNoCompare competitor backlinks at the main-domain level when true. Type: Boolean. Default: true.
min_intersectionsNoMinimum count of shared referring domains required for a backlink competitor. Type: Safe integer. Minimum: 1. Maximum: 10000000. Optional; no client default.
exclude_large_domainsNoExclude very large general-purpose domains from competitor recommendations when true. Type: Boolean. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.1.5
    • addedInput schema / properties / exclude_large_domains / description
      Added value: +"Exclude very large general-purpose domains from competitor recommendations when true. Type: Boolean. Default: true."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of backlink competitor records to return. Type: Safe integer. Minimum: 1. Maximum: 100. Default: 25."
    • addedInput schema / properties / main_domain / description
      Added value: +"Compare competitor backlinks at the main-domain level when true. Type: Boolean. Default: true."
    • addedInput schema / properties / min_intersections / description
      Added value: +"Minimum count of shared referring domains required for a backlink competitor. 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 / 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 / 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\", \"intersections\", \"opportunity\". Default: \"opportunity\"."
    • 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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=true. The description adds useful context that the tool 'Uses AgentSEO credits' and that repeating the call 'can create new charged work,' reinforcing the non-idempotent and costly nature. It still doesn't explain what the destructive aspect means beyond billing, but with annotations present, this is adequate.

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?

The description is two tight sentences with no redundant wording. The operational warning about credits is front-loaded after the purpose statement, though the first sentence is slightly jargon-heavy and could be plainer.

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?

Given nine parameters and no output schema, the description covers the core purpose and billing behavior but leaves out how competitors are selected, what the output contains, and how to interpret the overlap/authority/link-gap prioritization. The rich schema and annotations cover most structured details, making it minimally adequate but not complete.

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 the schema already documents all nine parameters, including sync, limit, offset, min_rank, and min_intersections. The description adds no parameter-level meaning beyond the schema, making the baseline 3 appropriate.

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 states a specific verb and resource: 'Discover backlink-profile competitors.' It is clear what the tool does, but it does not differentiate from adjacent siblings such as agentseo_backlinks_opportunity_finder or agentseo_domain_competitors, so an agent could pick the wrong one without comparing schemas.

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?

It implies research use through phrases like 'prioritize overlap, authority, and link-gap research actions,' but it never states when to choose this tool over the many sibling backlink tools. There are no exclusions or alternative recommendations.

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