Skip to main content
Glama
Sign In
mcp-wordpress

mcp-wordpress

by iamsamuelfraga
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_posts_get

Retrieve a single WordPress post by ID with full rendered HTML content. Choose edit, view, or embed context to get raw fields or public-facing version.

Instructions

Fetch a single blog post by ID. Returns the normalized post with full content (rendered HTML). Use context=edit (default) to include raw fields when available; context=view for the public-facing rendered version only.

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": {
      "id": "<id>"
    },
    "name": "wp_posts_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
contextNoedit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so the description carries full burden. It discloses the output format (rendered HTML, raw fields in edit) and the effect of context, but omits explicit read-only confirmation, error behavior, and permission requirements. Partial credit for adding behavioral context around context modes.

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 action, no fluff. Every sentence contributes to understanding the tool's purpose and key behavior.

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

Completeness4/5

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

For a simple get-by-id tool with only two parameters, the description covers the return payload and context behavior sufficiently. It lacks edge-case details like 404 handling or permissions, but these are not critical given the low complexity and clear scope.

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 coverage, the description explains the semantics of 'context' (edit/view) and default behavior, adding value beyond the schema. It does not explain 'embed' or elaborate on 'id', but 'id' is self-explanatory and the explanation covers the most important parameter.

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?

Clearly states it fetches a single blog post by ID, with a specific verb and resource. Distinguishes from sibling list/get tools by emphasizing single post and full content.

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 for selecting the 'context' parameter (edit vs view) and default behavior. However, it does not explicitly mention alternatives or exclusions relative to list tools, though the 'single post by ID' phrasing implies its use case.

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