MCP WordPress CrunchTools

Overview Schema Source Related Servers Discussions Admin

Wordpress Create Post

wordpress_create_post

Create a new WordPress post by specifying a title and content with optional fields like status, categories, and tags. Use it to publish, draft, or schedule posts directly through natural language.

Instructions

Create a new WordPress post.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	Publication date (ISO 8601 for scheduling, e.g., 2024-12-25T10:00:00)
`slug`	No	URL slug
`tags`	No	List of tag IDs
`title`	Yes	Post title
`status`	No	Post status - publish, draft, pending, private, future (default: draft)	draft
`content`	Yes	Post content (HTML or block format)
`excerpt`	No	Post excerpt
`categories`	No	List of category IDs
`post_format`	No	Format - standard, aside, gallery, link, image, quote, status, video, audio
`featured_media`	No	Featured image media ID

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.6.1Oct 17, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / categories / description
```
Added value: +"List of category IDs"
```
- addedInput schema / properties / content / description
```
Added value: +"Post content (HTML or block format)"
```
- addedInput schema / properties / date / description
```
Added value: +"Publication date (ISO 8601 for scheduling, e.g., 2024-12-25T10:00:00)"
```
- addedInput schema / properties / excerpt / description
```
Added value: +"Post excerpt"
```
- addedInput schema / properties / featured_media / description
```
Added value: +"Featured image media ID"
```
- addedInput schema / properties / post_format / description
```
Added value: +"Format - standard, aside, gallery, link, image, quote, status, video, audio"
```
- addedInput schema / properties / slug / description
```
Added value: +"URL slug"
```
- addedInput schema / properties / status / description
```
Added value: +"Post status - publish, draft, pending, private, future (default: draft)"
```
- addedInput schema / properties / tags / description
```
Added value: +"List of tag IDs"
```
- addedInput schema / properties / title / description
```
Added value: +"Post title"
```
First observedv0.5.0Aug 19, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing. It does not state that the post defaults to draft status, that scheduling is possible via date, whether the call requires authentication, or that it performs a write/mutation. Only the schema hints at the draft default.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of filler, but it is terse to the point of under-specification rather than efficiently concise. Nothing in the sentence is wasted, yet more could have earned its place.

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?

This is a 10-parameter mutation tool with no annotations and no usage guidance; an output schema exists so return values need no explanation. However, the description says nothing about the draft default, publishing behavior, permissions, or error conditions, leaving the definition inadequate for the tool's complexity.

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 100% and each of the 10 parameters has a meaningful, self-contained description (status enum values, ISO 8601 date format, tag/category ID lists). The description adds no parameter information beyond this, so the baseline of 3 applies.

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+resource ('Create a new WordPress post'), which cleanly separates it from wordpress_update_post, wordpress_get_post, and wordpress_create_page. It stops short of explicitly contrasting with the sibling create_page tool, so it is clear but not maximally differentiating.

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 wordpress_update_post (editing an existing post) or wordpress_create_page. Nothing is said about prerequisites such as authentication or required capability, so an agent must infer usage entirely from the name.

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