Skip to main content
Glama
Automattic

WordPress MCP

Official
by Automattic

create-post

Publish new WordPress posts with Gutenberg block formatting by specifying the title and structured content in block syntax for precise layout and design control.

Instructions

Create a new WordPress post using Gutenberg blocks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesPost content in WordPress block format. Here is an example of the format: If you given following blocks documentation: ``` Name: core/paragraph Title: Paragraph Description: Start with the basic building block of all narrative. Category: text ##Attributes ###align type: string ###content type: rich-text source: rich-text selector: p role: content ###dropCap type: boolean default: false ###placeholder type: string ###direction type: string enum: ltr,rtl ###lock type: object ###metadata type: object ###className type: string ###style type: object ###backgroundColor type: string ###textColor type: string ###gradient type: string ###fontSize type: string ###fontFamily type: string ###borderColor type: string ``` You can use the following format: ``` <!-- wp:paragraph {"align":"center", "dropCap":true, "direction":"ltr", "fontSize":"large", "fontFamily":"serif", "borderColor":"red", "backgroundColor":"blue", "textColor":"green", "gradient":"linear-gradient(to right, #000000, #ffffff)", "style":{"color":"red", "background-color":"blue"}} --> <p class="has-text-align-center has-drop-cap has-large-font-size has-serif-font-family has-border-color has-background has-text-color has-gradient has-global-padding has-global-margin has-global-color has-global-font-size" style="color:red;background-color:blue;">Your paragraph content here.</p> <!-- /wp:paragraph --> ```
titleYesPost title less than 70 characters
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Create' which implies a write/mutation operation, but doesn't disclose behavioral traits like required permissions, whether it publishes immediately, error handling, or rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in 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?

Single sentence, zero waste. It's front-loaded with the core purpose and includes a specific implementation detail ('using Gutenberg blocks') that adds value without verbosity. Every word earns 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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects (permissions, side effects), response format, or error conditions. Given the complexity of creating posts with Gutenberg blocks, more context is needed for effective agent use.

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%, so the schema already documents both parameters (title and content) with detailed examples and constraints. The description adds no parameter-specific information beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the action ('Create') and resource ('WordPress post') with the specific implementation detail 'using Gutenberg blocks'. It distinguishes from siblings like get-post (read) and update-post (modify), though not explicitly named. The purpose is specific but could more directly contrast with siblings.

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 on when to use this tool versus alternatives like update-post or search-posts. The description implies it's for new posts but doesn't state prerequisites (e.g., authentication, permissions) or exclusions (e.g., not for drafts). Usage context is implied but not explicit.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Automattic/wordpress-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server