wp-mcp-control-server

wp_create_page

Create WordPress pages directly by specifying title, HTML content, status, parent, template, and schedule. Publish instantly or save as draft.

Instructions

Create a new WordPress page

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>"
    },
    "name": "wp_create_page"
  }
}

Input Schema

Name	Required	Description	Default
`meta`	No
`slug`	No
`title`	Yes	Page title
`parent`	No
`status`	No		draft
`content`	No	HTML or Gutenberg block content
`excerpt`	No
`template`	No
`featured_media`	No
`scheduled_date`	No	ISO or parseable date string to schedule publication

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.3.0Aug 31, 2026

addedInput schema / properties / scheduled_date

Added value: +{
+  "description": "ISO or parseable date string to schedule publication",
+  "type": "string"
+}

First observedv1.0.0Jun 20, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'create.' It does not mention the default 'draft' status, whether scheduling via scheduled_date is supported, what happens with content format, or any required permissions/side effects.

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 sentence is short and front-loaded with the key action, which is efficient. However, given the tool's 10 parameters and lack of annotations, the description is under-sized rather than appropriately sized for the complexity.

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

Completeness1/5

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

The tool has 10 parameters, no annotations, and no output schema, yet the description offers only a minimal action statement. Missing critical context includes the default status, scheduling behavior, content expectations, and relationships with sibling page/post tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 30%, and the description adds no parameter meaning beyond what the schema already provides. Ten parameters exist, but the description explains none of them, so an agent would have to rely entirely on the schema.

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 specific verb (create) and resource (WordPress page), so an agent knows the core operation. However, it does not differentiate this tool from siblings like wp_create_post or wp_create_landing_page, which could create similar content.

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 about when to use this tool versus alternatives such as wp_create_post, wp_create_landing_page, or wp_elementor_create_blank_page. The description implies usage for creating pages but provides no exclusions or selection criteria.

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

Deploy Server