wordpress-mcp-server

Create a draft post

create_draft_post

Create a new WordPress post as a draft for human review without publishing or changing existing content.

Instructions

Create a new post as a DRAFT for a human to review. This tool cannot publish, edit or delete existing 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": {
      "title": "<title>",
      "content": "<content>"
    },
    "name": "create_draft_post"
  }
}

Input Schema

Name	Required	Description
`title`	Yes
`content`	Yes	Post body as HTML or plain text
`excerpt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations cover the safety profile (destructiveHint=false, readOnlyHint=false) but do not convey that the output is an unpublished draft requiring human review; the description supplies that workflow context. Silent on permissions required, duplicate handling (non-idempotent per annotations), and what the call returns, but the draft-vs-published distinction is the material addition here.

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 short sentences, both front-loaded: the primary action and state come first, the negative scope second. No filler or redundant phrasing.

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 three-parameter creation tool with no output schema, the description covers the key state distinction (draft, not published) but leaves the optional excerpt unexplained and says nothing about what the tool returns or whether the draft appears in list_posts. Adequate but with visible gaps given the low schema coverage.

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% – only 'content' is annotated, while 'title' and the optional 'excerpt' (max 1000 chars) are undocumented. The description adds no parameter meaning whatsoever, so it fails to compensate for the low coverage, particularly for what 'excerpt' is meant to contain.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a new post') and immediately narrows scope to 'as a DRAFT for a human to review'. The follow-up sentence explicitly rules out publishing, editing, and deleting, which cleanly separates it from the read-oriented siblings get_post, list_posts, get_site_info, and list_plugins.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description gives a clear usage context (content intended to be reviewed by a human before going live) plus explicit exclusions ('cannot publish, edit or delete existing content'). It stops short of naming a specific alternative tool for publishing or editing, so it earns a 4 rather than a 5.

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

Deploy Server