AgentSEO MCP Server

AgentSEO Domain Traffic Estimate

agentseo_domain_traffic_estimate

Destructive

Compare estimated search traffic across multiple domains, subdomains, or URLs before spending analysis credits. Sort results by organic, paid, or total traffic to prioritize targets.

Instructions

Compare estimated search traffic across multiple domains, subdomains, or URLs before spending deeper analysis credits. 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": {
      "targets": "<targets>"
    },
    "name": "agentseo_domain_traffic_estimate"
  }
}

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.
`sort_by`	No	Metric used to order returned results; choose one of this tool’s accepted enum values. Type: String. Accepted values: "organic_traffic", "total_traffic", "paid_traffic", "opportunity", "target". Default: "organic_traffic".	organic_traffic
`targets`	Yes	Domains, subdomains or URLs to compare; provide the target formats supported by this workflow. Type: Array. Minimum: 1 items. Maximum: 100 items. Required.
`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
`include_paid`	No	Include estimates for paid-search traffic when true; this does not buy ads. Type: Boolean. Default: true.
`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.
`include_local_pack`	No	Include local-pack contributions in the returned estimates when supported. Type: Boolean. Default: false.
`include_featured_snippet`	No	Include featured-snippet contributions in the returned estimates when supported. Type: Boolean. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.1.5Nov 5, 2026

addedInput schema / properties / include_featured_snippet / description

Added value: +"Include featured-snippet contributions in the returned estimates when supported. Type: Boolean. Default: true."

addedInput schema / properties / include_local_pack / description

Added value: +"Include local-pack contributions in the returned estimates when supported. Type: Boolean. Default: false."

addedInput schema / properties / include_paid / description

Added value: +"Include estimates for paid-search traffic when true; this does not buy ads. Type: Boolean. Default: true."

addedInput schema / properties / language / description

Added value: +"Supported search language code, for example en for English. Type: String. Default: \"en\"."

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

Added value: +"Metric used to order returned results; choose one of this tool’s accepted enum values. Type: String. Accepted values: \"organic_traffic\", \"total_traffic\", \"paid_traffic\", \"opportunity\", \"target\". Default: \"organic_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 / targets / description

Added value: +"Domains, subdomains or URLs to compare; provide the target formats supported by this workflow. Type: Array. Minimum: 1 items. Maximum: 100 items. Required."

addedInput schema / properties / targets / items / description

Added value: +"One domain, subdomain or absolute page URL included in the comparison. Type: String. Minimum: 1 characters. Required."

First observedv0.1.4Nov 4, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already flag non-idempotent, destructive, open-world behavior, and the description adds genuinely new context: the call consumes AgentSEO credits and repeating it can create a second charged job. That is exactly the kind of cost caution annotations can't express, though it doesn't explain what a 'charged work' repeat looks like in practice.

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, front-loaded with the capability and followed by the cost caveat. Nothing is redundant and nothing could be cut without losing information.

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 tool with no output schema, the description never indicates what the returned comparison contains (fields, per-target granularity) or how pending jobs surface in results. The schema covers inputs and the sync caveat, but the return side is left entirely unspecified.

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 all nine parameters, including the sort enum and the sync/polling caveat, are already documented in the schema. The description adds no parameter-level meaning beyond that, which is the expected baseline here.

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 ('Compare estimated search traffic across multiple domains, subdomains, or URLs'), which clearly separates it from detail-oriented siblings such as agentseo_domain_ranked_keywords or agentseo_domain_competitors. It stops short of naming any sibling, so the differentiation is implicit rather than explicit.

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?

'Before spending deeper analysis credits' implies a triage role in a workflow, but no alternative tool is named and no explicit when-not-to-use condition is given. An agent can infer usage but must still reason about which sibling to pick for deeper analysis.

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

Deploy Server