Skip to main content
Glama

wp_seo_keyword_research

Research a seed keyword to receive suggestions with variations and questions, leveraging competition analysis for relevant terms.

Instructions

Research keywords and get suggestions based on topic and competition analysis

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteNoSite identifier for multi-site setups
seedKeywordYesSeed keyword or topic to research
includeVariationsNoInclude keyword variations and long-tail keywords
includeQuestionsNoInclude question-based keywords
maxResultsNoMaximum number of keyword suggestions
Behavior2/5

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

With no annotations, the description fails to disclose whether the tool is read-only, if it calls external APIs, or any rate limits or side effects. The mention of 'competition analysis' hints at potential external data sources but is too vague to be transparent.

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?

The description is a single sentence, concise and front-loaded, containing no redundant information. Every word contributes to the core purpose, making it highly efficient for quick understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema and annotations, the description is too brief. It does not explain what the output contains (e.g., keyword lists, metrics), how competition analysis is performed, or any limitations. For a tool with 5 parameters, more contextual completeness is needed to enable effective use.

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?

All 5 parameters are described in the input schema with 100% coverage, so the baseline is 3. The description adds minimal extra meaning by mentioning 'topic and competition analysis,' which maps to seedKeyword but not directly to other parameters. It provides no new parameter-level semantics beyond the schema.

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 clearly states the tool researches keywords and provides suggestions based on topic and competition, using specific verbs and resources. Among sibling tools, there is no other keyword research tool, so it stands out, though the description could be more specific about how it differs from other SEO tools.

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?

No guidance is provided on when to use this tool versus alternatives such as wp_seo_analyze_content. The description lacks context for appropriate usage, prerequisites, or exclusions, leaving the agent without decision support.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/docdyhr/mcp-wordpress'

If you have feedback or need assistance with the MCP directory API, please join our Discord server