MCP Hub

Overview Schema Source Related Servers Discussions Admin

WordPress: Create post

wordpress_create_post

Create a new WordPress post with title, content, slug, categories, tags, featured image, and custom metadata. Set status and language for multilingual publishing.

Instructions

[UNIFIED] Create a new WordPress post. Supports custom slug, categories, tags, featured image, REST-registered post meta, and generic multilingual metadata.

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

Input Schema

Name	Required	Default
`meta`	No
`site`	Yes
`slug`	No
`tags`	No
`title`	Yes
`status`	No	draft
`content`	Yes
`excerpt`	No
`language`	No
`categories`	No
`featured_media`	No
`translation_of`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv3.14.0Nov 12, 2026

addedInput schema / properties / language

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / meta

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / translation_of

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Changed1 schema field changedv3.13.1May 22, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedv3.4.0Mar 31, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already state readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds a feature list but does not disclose important behavior such as default publication status, duplicate handling, or permission requirements.

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

Conciseness4/5

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

The description is brief and front-loads the primary action. The [UNIFIED] tag and feature list are compact, though the latter is too terse to carry full parameter meaning.

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?

For a 12-parameter mutation tool with no output schema and 0% schema description coverage, the description is materially incomplete. It omits required parameter context, default status behavior, and enough parameter detail for an agent to invoke the tool confidently.

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%, so the description must carry the burden for 12 parameters. It mentions slug, categories, tags, featured image, post meta, and multilingual metadata, but it does not explain site, title, content, status, excerpt, language, or translation_of semantics, and it gives no format details for the parameters it names.

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 clear verb and resource: create a new WordPress post. It is easy to identify, but it does not explicitly distinguish this from sibling tools such as wordpress_create_custom_post or wordpress_create_page.

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 explicit guidance on when to use this tool versus wordpress_create_custom_post or wordpress_create_page. The description lists supported features but leaves the choice between sibling creation tools to inference.

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

Deploy Server