Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Get post

wordpress_get_post
Read-only

Retrieve a specific WordPress post by ID to access its full content, metadata, and author details for display, analysis, or editing workflows.

Instructions

[UNIFIED] Get a specific WordPress post by ID. Returns complete post data including content, metadata, and author information.

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

Input Schema

NameRequiredDescriptionDefault
siteYes
fieldsNo
post_idYes
meta_keysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.14.0
    • addedInput schema / properties / meta_keys
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
  2. Changed1 schema field changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observedv3.4.0

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint=true already establishes this as a safe read. The description adds useful scope about returned data (content, metadata, author), but says nothing about authentication, error behavior, pagination, or how optional selections affect the response.

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 compact sentences, front-loaded with the core operation and followed by the return scope. The "[UNIFIED]" prefix is minor noise but every substantive sentence earns its place.

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 return-value summary helps offset the missing output schema, and annotations cover the safety profile. However, for a four-parameter tool with completely undocumented parameters, the definition leaves important invocation details unaddressed.

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% across all four parameters. The description clarifies post_id implicitly via "by ID" and hints at metadata, but does not explain the required site parameter, the fields parameter's string format, or how meta_keys filters metadata, so it only partially compensates.

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 a specific WordPress post by ID") and indicates the shape of the return data. It does not explicitly distinguish itself from sibling readers such as wordpress_get_page, leaving a small differentiation gap.

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?

The description implies retrieval by ID but gives no explicit when-to-use guidance, no conditions for choosing this over wordpress_get_page or SEO-specific readers, and no prerequisites or exclusions.

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