Skip to main content
Glama
Sign In
AgentSEO MCP Server

AgentSEO MCP Server

by AgentSEO-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

AgentSEO Keyword Metrics Overview

agentseo_keyword_metrics_overview
Destructive

Scores supplied keywords with search metrics and page-priority guidance to help prioritize SEO targets and content decisions.

Instructions

Score a supplied keyword list with search metrics and page-priority guidance. 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": {
      "keywords": "<keywords>"
    },
    "name": "agentseo_keyword_metrics_overview"
  }
}

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.
sort_byNoMetric used to order returned results; choose one of this tool’s accepted enum values. Type: String. Accepted values: "priority", "search_volume", "cpc", "difficulty". Default: "priority".priority
keywordsYesSearch phrases to evaluate or associate with the supplied page. Type: Array. Minimum: 1 items. Maximum: 100 items. Required.
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.
min_search_volumeNoMinimum 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.

  1. Changed8 schema fields changedv0.1.5
    • addedInput schema / properties / keywords / description
      Added value: +"Search phrases to evaluate or associate with the supplied page. Type: Array. Minimum: 1 items. Maximum: 100 items. Required."
    • addedInput schema / properties / keywords / items / description
      Added value: +"One search keyword or phrase, not a comma-separated list. Type: String. Minimum: 1 characters. Maximum: 80 characters. Required."
    • 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 / 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: \"priority\", \"search_volume\", \"cpc\", \"difficulty\". Default: \"priority\"."
    • 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."
  2. First observedv0.1.4

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true; the description usefully reinforces this by disclosing that the call consumes AgentSEO credits and that a repeat invocation can start new billable work. That is genuine cost/non-idempotency context rather than paraphrase. It still omits what a partial or failed run costs and whether results are cached.

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 with the core action front-loaded and the cost caveat immediately after; nothing is padded. It is perhaps terse to the point of under-serving a seven-parameter paid tool, but no sentence is wasted.

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?

With no output schema, the description should indicate what comes back (per-keyword metrics, ordering, priority scoring), and it does not. It also mentions 'page-priority guidance' although no page parameter exists in the schema, which slightly muddies expectations about what input drives the scoring. Adequate as a one-line orientation, insufficient for a paid, non-idempotent analytics call.

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 seven parameters are already documented in the schema, including enum values for sort_by and the credit-related job-polling note on sync. The description adds only the notion of 'page-priority guidance', which loosely explains the default sort_by=priority. Baseline 3 is appropriate when the schema carries the load.

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: score a supplied keyword list with search metrics and page-priority guidance. That is enough to separate it from generation-oriented siblings like agentseo_keyword_ideas_suggest or agentseo_domain_ranked_keywords, which produce keyword sets rather than scoring a list the caller already holds. It stops short of naming any sibling explicitly.

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?

The phrase 'a supplied keyword list' weakly implies the precondition (you already have keywords), and 'repeating the call can create new charged work' warns against retries. But there is no explicit when-to-use, when-not-to-use, or alternative routing among the 40+ siblings, and the real guidance about polling agentseo_job_status lives only in the schema's sync parameter.

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