wordpress_get_postFetch a single WordPress post by ID and return its full content. Use it to retrieve specific post details for display, editing, or analysis.
Get a single WordPress post by ID with full content.
| Name | Required | Description | Default |
|---|---|---|---|
| post_id | Yes | Post ID |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.6.1Input schema / additionalPropertiesAdded value: +falseInput schema / properties / post_id / descriptionAdded value: +"Post ID"Input schema / properties / post_id / minimumAdded value: +1v0.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
readOnlyHint=true already establishes the safe read profile, so the description carries a lighter burden. It adds useful payload context ('full content', implying complete post body rather than a summary), but says nothing about permissions, drafts vs. published visibility, or error behavior for invalid IDs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with zero filler, front-loading the verb and resource immediately. Nothing could be trimmed without losing meaning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter read tool with an output schema that already describes the return shape, the description covers what an agent needs to select and invoke it. Only the absence of sibling routing keeps it short of complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single post_id parameter is fully documented in the schema, so the baseline is 3. The description's 'by ID' merely restates the parameter rather than adding format or constraint detail beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Get a single WordPress post by ID') and scopes the payload with 'full content'. This implicitly distinguishes it from list_posts and search_posts, though it never names those siblings explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'by ID' implies the tool is for direct retrieval when an identifier is known, and 'single' rules out bulk listing, but there is no explicit when-to-use statement or reference to alternatives like search_posts or get_page.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.