Skip to main content
Glama
Sign In
AgentSEO MCP Server

AgentSEO MCP Server

by AgentSEO-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

AgentSEO Keyword Ideas Suggest

agentseo_keyword_ideas_suggest
Destructive

Expands a seed keyword into prioritized long-tail keyword ideas with search metrics to guide keyword targeting. Poll the returned job ID for pending results instead of repeating charged calls.

Instructions

Expand one seed keyword into prioritized long-tail keyword ideas with search metrics. 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": {
      "keyword": "<keyword>"
    },
    "name": "agentseo_keyword_ideas_suggest"
  }
}

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 keyword suggestions to return. Type: Safe integer. Minimum: 5. Maximum: 100. Default: 25.
keywordYesSearch keyword or phrase to analyze for this workflow. Type: String. Minimum: 3 characters. 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
exact_matchNoRequest exact-match keyword filtering rather than broader phrase matching when true. Type: Boolean. Default: false.
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.
ignore_synonymsNoAsk the provider not to expand keyword matching to synonyms when true. Type: Boolean. Default: true.
min_search_volumeNoMinimum estimated monthly keyword searches to include; zero disables this lower-bound filter. Type: Safe integer. Minimum: 0. Maximum: 1000000. Default: 0.
include_seed_keywordNoInclude the original seed phrase among returned keyword ideas when true. Type: Boolean. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.1.5
    • addedInput schema / properties / exact_match / description
      Added value: +"Request exact-match keyword filtering rather than broader phrase matching when true. Type: Boolean. Default: false."
    • addedInput schema / properties / ignore_synonyms / description
      Added value: +"Ask the provider not to expand keyword matching to synonyms when true. Type: Boolean. Default: true."
    • addedInput schema / properties / include_seed_keyword / description
      Added value: +"Include the original seed phrase among returned keyword ideas when true. Type: Boolean. Default: true."
    • changedInput schema / properties / keyword / description
      Previous value: -"Seed keyword or topic"New value: +"Search keyword or phrase to analyze for this workflow. Type: String. Minimum: 3 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 / limit / description
      Added value: +"Maximum number of keyword suggestions to return. Type: Safe integer. Minimum: 5. Maximum: 100. 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 / 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 / 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

A3.7/5.0
Behavior4/5

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

Annotations already declare open-world, non-idempotent, non-read-only behavior, but the description adds important context: the tool consumes AgentSEO credits and repeating the call can create new charged work. It does not explain the destructiveHint or fuller job-flow consequences, but the credit/cost disclosure is substantive.

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 tight sentences with the core action front-loaded and the credit warning immediately after. There is no filler.

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 ten-parameter, charged, potentially asynchronous tool with no output schema, the description is minimal. It covers purpose and cost but does not explain usage alternatives, result shape, or the job-status path beyond what the schema already says.

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 ten parameters are already well documented in the schema. The description adds no parameter-level meaning beyond that, making the baseline score appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: expand one seed keyword into prioritized long-tail keyword ideas with search metrics. This is concrete enough to distinguish it from metrics-oriented or domain-keyword siblings.

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?

It gives no explicit when-to-use guidance versus siblings such as agentseo_keyword_metrics_overview or agentseo_search. The warning about repeating charged calls is useful, but it is a cost caution rather than a routing guideline.

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