wordpress-mcp-server

Get a post or page

get_post

Read-only

Retrieve a single WordPress post or page by ID and return its content as plain text, so agents can read specific content without fetching the full site.

Instructions

Fetch one post or page by ID, with its content as plain text.

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": "get_post"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`type`	No		posts

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered elsewhere. The description adds a genuine behavioral detail — content comes back as plain text rather than rendered markup — but says nothing about error behavior for bad IDs, missing posts, or whether page content differs from post content.

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?

A single well-formed sentence with the resource, selector, and output format front-loaded and no filler. It is arguably under-specified rather than over-long, but nothing in it is wasted.

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?

For a simple two-parameter read tool the definition is serviceable, and the absence of an output schema means return shape could use more explanation than the one phrase 'content as plain text'. It does not tell the agent what other fields (title, status, date) come back or how a nonexistent ID is reported.

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 0%, so the description carries the load: 'by ID' maps to the required id parameter, and 'post or page' maps to the type enum. It does not mention the 'posts' default or that IDs must be positive integers, so the compensation is partial.

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?

States a specific verb and resource ('Fetch one post or page'), scopes it to a single item by ID, and adds the return format ('content as plain text'), which separates it from the list_posts sibling. It does not explicitly name the alternative, so it stops short of a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance and no routing to list_posts or to creation siblings. The need for an ID implies the lookup scenario, but the agent must infer it rather than being told.

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

Deploy Server