Skip to main content
Glama
Sign In
MCP WordPress Server

MCP WordPress Server

by docdyhr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wp_seo_keyword_research

Research keywords and get suggestions by analyzing a seed topic against competition. Discover variations, long-tail keywords, and question-based terms.

Instructions

Research keywords and get suggestions based on topic and competition analysis

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": {
      "seedKeyword": "<seedKeyword>"
    },
    "name": "wp_seo_keyword_research"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.3.23
  2. Removedv3.3.22
  3. Addedv3.3.8
  4. Removedv3.3.7
  5. Changed1 schema field changedv3.3.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  6. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits (e.g., read-only, auth needs, effect on data). It does not, offering only the basic function.

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?

Single sentence that is front-loaded and concise. Every word adds value, though minor refinements could improve clarity.

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?

With 5 parameters, no output schema, and no annotations, the description lacks completeness. It does not explain output format, competition analysis interpretation, or error states.

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 parameters are documented in the schema. The description adds no extra meaning beyond the parameter descriptions, meeting the baseline.

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 uses a specific verb ('Research') and resource ('keywords'), and mentions 'topic and competition analysis', clearly distinguishing this from sibling tools like site audits or content analysis.

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 when-to-use or when-not-to-use guidance is provided. The description implies general keyword research but does not exclude alternatives or specify prerequisites.

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