Skip to main content
Glama
Sign In
AgentSEO MCP Server

AgentSEO MCP Server

by AgentSEO-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

AgentSEO Domain Competitors

agentseo_domain_competitors
Destructive

Discover search competitors for a domain, prioritize them by keyword overlap, traffic gaps, or threat, and identify next analysis actions.

Instructions

Discover search competitors for a domain and prioritize overlap, traffic gaps, and next analysis 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_domain_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 competing domain records to return. Type: Safe integer. Minimum: 5. Maximum: 250. Default: 25.
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: "overlap", "competitor_traffic", "traffic_gap", "threat". Default: "threat".threat
languageNoSupported search language code, for example en for English. Type: String. Default: "en".en
locationNoSupported geographic search-market name, for example United States; this is not a coordinate pair. Type: String. Default: "United States".United States
location_codeNoNumeric provider location identifier for the search market; the service validates support alongside the location name. Type: Safe integer. Must be greater than 0. Optional; no client default.
max_rank_groupNoWorst search position included when measuring competitor overlap, where 1 means first. Type: Safe integer. Minimum: 1. Maximum: 100. Default: 20.
min_intersectionsNoMinimum count of shared ranking keywords required for a search competitor. Type: Safe integer. Minimum: 0. Maximum: 10000000. Default: 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.1.5
    • addedInput schema / properties / language / description
      Added value: +"Supported search language code, for example en for English. Type: String. Default: \"en\"."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of competing domain records to return. Type: Safe integer. Minimum: 5. Maximum: 250. Default: 25."
    • addedInput schema / properties / location / description
      Added value: +"Supported geographic search-market name, for example United States; this is not a coordinate pair. Type: String. Default: \"United States\"."
    • addedInput schema / properties / location_code / description
      Added value: +"Numeric provider location identifier for the search market; the service validates support alongside the location name. Type: Safe integer. Must be greater than 0. Optional; no client default."
    • addedInput schema / properties / max_rank_group / description
      Added value: +"Worst search position included when measuring competitor overlap, where 1 means first. Type: Safe integer. Minimum: 1. Maximum: 100. Default: 20."
    • addedInput schema / properties / min_intersections / description
      Added value: +"Minimum count of shared ranking keywords required for a search competitor. Type: Safe integer. Minimum: 0. Maximum: 10000000. 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: \"overlap\", \"competitor_traffic\", \"traffic_gap\", \"threat\". Default: \"threat\"."
    • 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

A3.6/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, and destructive, so the bar is lower. The description still earns credit by naming the credit cost and that repeating creates new charged work, which is commercial behavior the annotations cannot express. It does not mention the pending-job/status-poll outcome, though the schema's sync parameter does.

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 short sentences, front-loaded with the purpose, followed by the cost warning. The phrase 'next analysis actions' is slightly vague filler, but nothing is redundant or padded.

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 nine-parameter, credit-consuming, non-idempotent tool with no output schema, the description says nothing about what a competitor record contains or how the sort metrics differ. Annotations plus schema cover safety and parameters, but the agent still has no picture of the return shape or the pending-job workflow beyond the sync field's own text.

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 coverage is 100%, so every parameter including sync, sort_by enum values, and max_rank_group is already documented. The description adds no syntax, defaults, or interpretation beyond that, so the baseline 3 applies.

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 ('Discover search competitors for a domain') plus the analytic framing (overlap, traffic gaps). It is distinguishable from agentseo_backlinks_competitors and agentseo_domain_intersection in intent, but it never names those siblings, so the distinction relies on inference.

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 'prioritize overlap, traffic gaps' wording implies when this tool is the right starting point, and the credits warning implies caution about repeats. It gives no explicit when-not guidance and does not route the agent to alternatives like agentseo_domain_intersection or agentseo_domain_ranked_keywords.

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

Deploy Server

Other Tools