AgentSEO MCP Server

AgentSEO Domain Relevant Pages

agentseo_domain_relevant_pages

Destructive

Identify a domain's traffic-carrying pages and sort them into protect, refresh, expand, or recover actions for SEO planning.

Instructions

Find traffic-carrying pages for a domain and route them into protect, refresh, expand, or recover 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_relevant_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 traffic-carrying page records to return. Type: Safe integer. Minimum: 10. Maximum: 250. Default: 50.
`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: "estimated_traffic", "keyword_count", "top3", "opportunity". Default: "estimated_traffic".	estimated_traffic
`language`	No	Supported search language code, for example en for English. Type: String. Default: "en".	en
`location`	No	Supported geographic search-market name, for example United States; this is not a coordinate pair. Type: String. Default: "United States".	United States
`min_traffic`	No	Minimum estimated monthly organic search visits a page must have; zero disables this lower-bound filter. Type: Safe integer. Minimum: 0. Maximum: 10000000. Default: 0.
`location_code`	No	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.
`historical_serp_mode`	No	Whether to use live, lost or all supported historical search-ranking observations. Type: String. Accepted values: "live", "lost", "all". Default: "live".	live

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.1.5Nov 5, 2026

addedInput schema / properties / historical_serp_mode / description

Added value: +"Whether to use live, lost or all supported historical search-ranking observations. Type: String. Accepted values: \"live\", \"lost\", \"all\". Default: \"live\"."

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 traffic-carrying page records to return. Type: Safe integer. Minimum: 10. Maximum: 250. Default: 50."

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 / min_traffic / description

Added value: +"Minimum estimated monthly organic search visits a page must have; zero disables this lower-bound filter. 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: \"estimated_traffic\", \"keyword_count\", \"top3\", \"opportunity\". Default: \"estimated_traffic\"."

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.8/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 and openWorldHint=true; the description adds materially useful context beyond them by disclosing that the call consumes AgentSEO credits and that repeating it can spawn new charged work. What it does not do is explain why destructiveHint is true (what is created or overwritten by the protect/refresh/expand/recover routing), so the safety picture is only partly filled in.

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 sentences, both front-loaded and non-redundant: the first gives purpose and downstream behavior, the second gives the cost/idempotency warning an agent most needs before calling. Nothing repeats the schema or annotations verbatim.

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?

For a 9-parameter charged, non-idempotent tool the description covers the two things structured fields do not: credit cost and repeat-call risk, and it hints at the routing output despite there being no output schema. The remaining gap is minor — the description does not clarify what the destructive hint actually means in terms of created or modified state.

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 every parameter (target, limit, min_traffic, sort_by, sync, location, language, historical_serp_mode, location_code) is already documented in the schema, including enums and defaults. The description adds no parameter-level meaning such as target formatting rules or the effect of sort_by on action routing, so 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 ('find traffic-carrying pages for a domain') plus the follow-on behavior ('route them into protect, refresh, expand, or recover actions'). It is distinguishable from siblings like agentseo_domain_ranked_keywords or agentseo_domain_traffic_estimate by the page-level, action-routing framing, though no sibling is named explicitly.

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?

Usage is only implied: the tool is for domain page discovery with action routing. There is no explicit when-to-use vs when-not guidance, no statement of prerequisites, and no pointer to an alternative sibling (e.g., ranked keywords or traffic estimate) for cases where page-level routing is not what the agent wants.

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

Deploy Server