Skip to main content
Glama

wp_create_post

Create a WordPress post as a draft from a title and content, respecting write-mode permissions so AI agents can stage content before publishing.

Instructions

Create a WordPress post. Always created as a draft unless the owner has allowed otherwise. Requires write mode.

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": {
      "title": "<title>",
      "content": "<content>"
    },
    "name": "wp_create_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
contentYesHTML or block markup
excerptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/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 it does disclose two substantive facts: the post lands as a draft unless the owner permits otherwise, and write mode is a prerequisite. It omits what the call returns (e.g. a post ID needed for later updates), failure behavior, and whether duplicate titles are allowed.

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?

Three short sentences, front-loaded with the purpose, then the draft constraint, then the mode requirement. No filler, no repetition of the tool name, and each sentence adds a distinct fact.

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 mutation tool with no annotations and no output schema, the description covers the key surprise (it will not go live) and the access prerequisite, which is genuinely useful. However, it leaves the agent without return-value expectations and without guidance on the publish path, which matters for a create operation in a CMS.

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 only 33% and the description says nothing about any of the three parameters. Title and excerpt are undocumented in both the schema and the description, and the only schema hint (content is HTML or block markup) is not reinforced or clarified in the description.

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?

The description states a specific verb and resource ("Create a WordPress post"), which cleanly separates it from wp_update_post, wp_trash_post, and wc_create_product by both verb and target object. It stops short of explicitly naming or contrasting a sibling, so a 4 rather than 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the draft-by-default note hints that this is for staging content rather than publishing. There is no explicit when-to-use versus when-not-to-use guidance, no mention of how to publish afterward, and no named alternative for that follow-up.

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