AgentSEO MCP Server

AgentSEO Domain Ranked Keywords

agentseo_domain_ranked_keywords

Destructive

Find ranked keywords for a domain, subdomain, or URL, then prioritize refresh opportunities by opportunity, traffic, rank, search volume, or CPC.

Instructions

Find ranked keywords for a domain, subdomain, or URL and prioritize refresh opportunities. 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_ranked_keywords"
  }
}

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 ranked keyword 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: "opportunity", "estimated_traffic", "rank", "search_volume", "cpc". Default: "opportunity".	opportunity
`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
`max_rank`	No	Worst organic search position to include, where 1 means first. Type: Safe integer. Minimum: 1. Maximum: 100. Default: 100.
`include_lost`	No	Include historically lost ranking keywords when true. Type: Boolean. Default: false.
`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.
`min_search_volume`	No	Minimum estimated monthly keyword searches to include; zero disables this lower-bound filter. Type: Safe integer. Minimum: 0. Maximum: 1000000. Default: 0.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.1.5Nov 5, 2026

addedInput schema / properties / include_lost / description

Added value: +"Include historically lost ranking keywords when true. Type: Boolean. Default: false."

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 ranked keyword 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 / max_rank / description

Added value: +"Worst organic search position to include, where 1 means first. Type: Safe integer. Minimum: 1. Maximum: 100. Default: 100."

addedInput schema / properties / min_search_volume / description

Added value: +"Minimum estimated monthly keyword searches to include; zero disables this lower-bound filter. Type: Safe integer. Minimum: 0. Maximum: 1000000. 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: \"opportunity\", \"estimated_traffic\", \"rank\", \"search_volume\", \"cpc\". 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."

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 declare non-read-only, non-idempotent, open-world, and destructive behavior, so the description's added value is the credit-cost disclosure ('Uses AgentSEO credits; repeating the call can create new charged work'), which meaningfully reinforces the non-idempotent hint. It stops short of saying how many credits or what the destructive surface actually is, keeping it below a 5.

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 short sentences with zero filler: purpose first, cost caveat second. Every clause carries information an agent needs before calling a charged endpoint.

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 10-parameter, credited, open-world tool with no output schema, the definition is serviceable but thin: it never indicates what a 'ranked keyword' record contains beyond the sort metrics implied by the enum, nor what a pending/queued response looks like. The schema carries parameter documentation and the sync param covers the polling path, which prevents this from being inadequate.

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% and each of the 10 parameters is documented in-schema, including the sync/polling caveat, so the schema does the heavy lifting. The description only lightly mirrors the 'domain, subdomain, or URL' semantics of target and adds no format or interaction detail beyond the schema, making the baseline 3 correct.

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 ('Find ranked keywords') plus accepted target types (domain, subdomain, or URL) and a secondary purpose ('prioritize refresh opportunities'). It is clear on its own, but it never names or contrasts with near siblings such as agentseo_domain_relevant_pages, agentseo_keyword_metrics_overview, or agentseo_rank_track, so an agent must infer the boundary from the name alone.

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 context is only implied: 'prioritize refresh opportunities' hints at the refresh workflow, and the credit warning hints at cost sensitivity. There is no explicit statement of when to choose this over the many sibling domain/keyword tools, and no stated prerequisites or exclusions.

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

Deploy Server