Skip to main content
Glama
ArsNovaSingers

ars-nova-wordpress-mcp

Official

Create WordPress Post

wp_create_post

Create a WordPress post with full control over title, content, status, categories, tags, and scheduling. Defaults to draft for safety; set status to publish to publish immediately.

Instructions

Create a new blog post. Defaults to status='draft' for safety — set status='publish' to publish immediately.

Args:

  • title (string): Post title.

  • content (string): HTML body.

  • excerpt (string): Optional short summary.

  • slug (string): URL slug. Auto-generated from title if omitted.

  • status (enum): publish | future | draft | pending | private. Default 'draft'.

  • author (number): Author user ID. Defaults to authenticated user.

  • featured_media (number): Featured image media ID.

  • date (string): ISO 8601 schedule date. Set status='future' for scheduling.

  • categories (number[]): Category IDs.

  • tags (number[]): Tag IDs.

  • response_format (enum): markdown | json. Default 'markdown'.

Returns: The created WPContentItem (id, slug, status, link, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoPublish/schedule date in ISO 8601 (e.g. '2026-05-15T10:00:00'). For scheduling, also set status='future'.
slugNoURL slug. WP auto-generates from title if omitted on create.
tagsNoTag IDs to assign. Replaces existing on update.
titleNoPost/page title (plain text).
authorNoAuthor user ID. Defaults to the authenticated user on create.
statusNoStatus. Defaults to 'draft' for safety. Set to 'publish' to publish immediately.draft
contentNoPost/page HTML content. Send <p>, <h2>, <a>, <img>, etc. WP renders inline.
excerptNoShort summary shown on archive/listing pages.
categoriesNoCategory IDs to assign. Replaces existing on update.
featured_mediaNoFeatured image media ID. Use 0 to unset.
response_formatNoOutput format: 'markdown' for human-readable, 'json' for machine-readable.markdown
Behavior4/5

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

The description enriches the annotations by explicitly stating 'Defaults to status="draft" for safety' and explaining that 'set status="publish" to publish immediately.' It also discloses slug auto-generation and scheduling behavior. These are meaningful behavioral traits beyond the basic write indication from readOnlyHint=false and destructiveHint=false. The return format is also stated, adding further transparency.

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 clearly structured with 'Args' and 'Returns' sections, front-loading the core purpose and safety default. It is somewhat lengthy and partially duplicates the schema, but every sentence adds contextual value for an agent, and the formatting aids quick scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 11 parameters, no output schema, and minimal annotations, the description is remarkably complete. It covers all parameters, defaults, scheduling, return value (WPContentItem with id, slug, status, link, etc.), and safety defaults. This provides an agent with everything needed to invoke the tool correctly.

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?

With 100% schema description coverage, the schema already fully documents all parameters. The description repeats the args but adds no new meaning beyond the schema (e.g., slug auto-generation is already in the schema). It meets the baseline but does not elevate it.

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?

The description opens with 'Create a new blog post' – a specific verb+resource statement that clearly distinguishes from siblings like wp_create_page, wp_update_post, and wp_delete_post. It reinforces the scope with detailed parameter guidance and a return value description, leaving no ambiguity about what the tool does.

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

Usage Guidelines3/5

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

The description offers clear context on how to use the tool (e.g., defaults to draft for safety, set status='publish' to publish, set status='future' for scheduling), but it does not explicitly mention when to use this tool over alternatives like wp_create_page or wp_update_post. No when-not or alternative guidance is provided, so it falls short of a 4.

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

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/ArsNovaSingers/ars-nova-wordpress-mcp'

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