Skip to main content
Glama

royal-mcp__wp_create_page

Destructive

Create new page. Combine status="future" with date to schedule. Excerpt (via wp_update_post_meta on _excerpt or via wp_create_post fallback) may contain safe HTML. (site: demo.royalplugins.com) Through Royally: waits for a person to approve it in Royally; nothing on the site changes until then.

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": "royal-mcp__wp_create_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoISO 8601 datetime in the site timezone (e.g. 2026-12-25T09:00:00). Combine with status=future to schedule.
titleYes
parentNoParent page ID
statusNo
contentYes
site_idNoSite to run this tool on: 8ef2e52b-bd07-4671-a363-ebe8b480b65c (https://demo.royalplugins.com)
templateNoPage template: default, or a template filename the theme offers for pages. Anything else is refused and the error lists the valid values.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / template
      Added value: +{
      +  "description": "Page template: default, or a template filename the theme offers for pages. Anything else is refused and the error lists the valid values.",
      +  "type": "string"
      +}
  2. Added
  3. Removed
  4. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The most valuable addition is the disclosure that the operation is staged for human approval and 'nothing on the site changes until then' — that materially changes how an agent should report success. Beyond that, the description is muddled: the 'Excerpt (via wp_update_post_meta on _excerpt or via wp_create_post fallback)' sentence refers to workflow that has no corresponding parameter in the schema, and it does not describe what a successful response contains or whether the page is created in draft state pending approval.

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 definition is short, and the approval constraint is placed last rather than front-loaded. The excerpt parenthetical is dense and references tools/fields that do not appear in this schema, which costs the reader more than it earns.

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

Completeness3/5

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

For a 7-parameter mutation tool with no output schema and destructiveHint=true, the description supplies the crucial approval-workflow context but omits output expectations (page ID, status, approval token) and content-format expectations. An agent can call it, but cannot predict the result shape or how to report it.

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 coverage is 57%, and the schema already documents date, parent, site_id, and the template refusal behavior. The description repeats the status=future + date rule rather than adding to it, and leaves title and content undocumented while making no mention of the parent or template parameters. Baseline 3 fits since the schema carries most of the load.

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 opening clause 'Create new page' gives a specific verb and resource, so the agent immediately knows this is a page-creation tool. It does not distinguish itself from the very similar sibling wp_create_post (posts vs. pages), which is the one differentiation that matters most in this tool set.

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 scheduling rule ('Combine status="future" with date to schedule') is clear when-to-use guidance for one parameter combination, and the Royally approval note tells the agent what happens after the call. There is no explicit guidance on choosing this tool over wp_create_post, wp_update_page, or wp_create_preview_link.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources