Skip to main content
Glama
Sign In
mcp-wordpress

mcp-wordpress

by iamsamuelfraga
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_seo_analyze_post

Analyzes WordPress post SEO: readability (Flesch-Kincaid EN/ES/PT), keyword density, heading hierarchy, length stats. Optionally reports focus keyword presence and density.

Instructions

Run SEO/content analysis on a post: readability (Flesch-Kincaid in ES/EN/PT), keyword density, headings hierarchy lint, content length stats. Optionally pass focus_keyword to get presence stats (in title, first paragraph, headings) and density of that exact term.

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": {
      "post_id": "<post_id>"
    },
    "name": "wp_seo_analyze_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes
languageNo
focus_keywordNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the analyses performed and the optional keyword behavior, but doesn't state whether the tool is read-only, return format, or defaults (e.g., what happens if language is omitted).

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 sentences, front-loaded with the verb, no redundancy. Every phrase adds value.

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?

The tool has no output schema, so the description should explain return values; it mentions stats but not structure or defaults. Overall it covers main functionality but leaves operational details unclear.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description compensates by explaining focus_keyword (presence stats and density) and language (ES/EN/PT readability). post_id is implied by 'on a post' but not explicitly detailed.

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?

Description clearly states the tool runs SEO/content analysis on a post, listing specific checks (readability, keyword density, headings hierarchy, content length), which distinguishes it from siblings like wp_seo_get_meta or wp_seo_detect_provider.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context that this is for analyzing a post's SEO/content quality, and explains optional focus_keyword usage. However, it doesn't explicitly mention alternatives or when not to use this tool versus other SEO tools.

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