Skip to main content
Glama

ADS Beast

seo_keyword_research

Read-only

Keyword clusters with intent, priority and AI-citation potential for a topic. AI: 1 AI request.

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": {
      "topic": "<topic>"
    },
    "name": "seo_keyword_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
geoNoCountry code, e.g. us or de.
topicYesTopic, product or service.
languageNoLanguage code, e.g. en.
client_idNo
seed_keywordsNoSeed keywords, comma-separated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the burden is lower. The description adds one genuinely new behavioral fact, the cost ('AI: 1 AI request'), which annotations do not express, but it says nothing about latency, coverage limits, or how many clusters come back.

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 terse fragments with zero filler, and the delivered fields are front-loaded before the cost note. Nothing could be removed 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?

With no output schema, the description does helpfully enumerate the returned fields, which is the main thing an agent needs. But for a 5-parameter open-world research tool it leaves unclear whether it operates on the caller's own site or the open web, and how the optional client_id and seed_keywords alter behavior.

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 80%, so the schema already explains topic, geo, language, and seed_keywords; the description adds nothing about them. The one undocumented parameter, client_id, receives no explanation anywhere, though the description does not make that worse.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (keyword clusters) and the output fields (intent, priority, AI-citation potential) scoped to a topic, which distinguishes it from siblings like seo_keywords_track or seo_keyword_rank_check. However, it is a noun phrase with no verb, so it never says whether it generates, fetches, or analyzes the clusters.

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?

There is no when-to-use guidance and no named alternative; the agent must infer from the phrase 'for a topic' that this is the discovery step rather than tracking or rank checking. No prerequisites or exclusions are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.