AutoWP MCP Server

create-blog-post

Create a WordPress blog post by providing title and HTML content, with optional excerpt, categories, tags, and publication status.

Instructions

Create a blog post in WordPress

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-blog-post"
  }
}

Input Schema

Name	Required	Description	Default
`tags`	No	Array of tag IDs
`title`	Yes	The title of the blog post
`status`	No	Publication status	draft
`content`	Yes	The HTML content of the blog post
`excerpt`	No	Optional post excerpt/summary
`categories`	No	Array of category IDs

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 31, 2026

TDQS

C2.7/5.0

Behavior1/5

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

With no annotations available, the description must disclose behavioral traits. It only says 'create' and omits critical details: posts default to 'draft' status (per schema), authentication requirements, whether it returns the created post, or any side effects. For a mutation tool, this is a severe lack of transparency.

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?

The description is a single sentence with no wasted words. It is front-loaded with the action and purpose, making it extremely concise and easy to parse.

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?

Despite full schema coverage, the description lacks essential behavioral context: no mention of the default draft status, return value, or how it fits with sibling tools. There is no output schema or annotations to compensate, so the agent has insufficient information for a create operation with 6 parameters.

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?

The input schema provides descriptions for all 6 parameters, covering 100% of them, so the baseline is 3. The description adds no parameter-level detail, but the schema handles the semantics adequately, including defaults and enums.

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 uses a specific verb+resource ('Create a blog post') and names the platform ('in WordPress'), making the core function clear. However, it does not explicitly differentiate from sibling tools like save-draft, which may have overlapping functionality for creating draft posts.

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?

No guidance is provided on when to use this tool versus alternatives such as save-draft, schedule-post, or update-post. The description only states what it does, leaving the agent to infer usage context without explicit conditions or exclusions.

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