Skip to main content
Glama

wp_get_post

Retrieve a single WordPress post by ID, including its content, to read post details for AI or automation workflows.

Instructions

Get one WordPress post, including its content.

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_get_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: it does not say what happens when the ID does not exist, whether drafts/private posts are returned, whether auth is required, or what fields come back. "Including its content" is the sole behavioral detail, and read-only status is only implied by the verb "Get."

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?

One short, front-loaded sentence with no filler or repetition. It is efficient, though the terseness borders on under-specification rather than being a model of informative brevity.

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?

No annotations, no output schema, and an undocumented parameter mean the description is the only source of context, and it supplies almost none. For a lookup tool whose failure modes (missing ID, permission errors, draft visibility) matter to correct invocation, this is thin.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter, so the description needed to compensate and does not. It never clarifies whether "id" is a post ID (integer, per the schema), a slug, or a globally-unique identifier across post types, which is a real ambiguity for WordPress APIs.

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 ("Get one WordPress post") and scopes it to a single item, which implicitly separates it from list-style siblings such as wp_list_posts. It also names one concrete payload element ("including its content"). No sibling is named explicitly, so it falls 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 guidance on when to use this versus wp_list_posts, wp_get_post vs a filtered list, or any prerequisite. The only implicit cue is "one post," leaving the agent to infer selection criteria entirely.

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