Skip to main content
Glama

royal-mcp__wp_update_post

Destructive

Update existing post (any post type). Response includes saved_fields (actual stored values, read back from DB) so silent-drop / silent-modify by WordPress is surfaced rather than hidden. Pass date to reschedule or backdate. Backslashes (JSON unicode escapes, embedded JSON-LD, Divi loop field bindings) are stored as sent. A content, title or excerpt that a read shows in part hidden (a key in an embed, a credential in text) is not replaced as a whole (read_is_masked): change the text around it with wp_replace_in_post, whose find text may not touch the hidden part. (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": {
      "id": "<id>"
    },
    "name": "royal-mcp__wp_update_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
dateNoISO 8601 datetime in the site timezone (e.g. 2026-12-25T09:00:00). Combine with status=future to reschedule, or use alone to backdate.
titleNo
statusNo
contentNo
excerptNoOptional excerpt. May contain safe HTML (same allow-list as post content).
site_idNoSite to run this tool on: 8ef2e52b-bd07-4671-a363-ebe8b480b65c (https://demo.royalplugins.com)
passwordNoPost password. Empty string removes protection.
menu_orderNoOrder among sibling posts/pages. Lower = earlier.
ping_statusNoAllow (open) or disallow (closed) trackbacks / pingbacks.
post_authorNoUser ID to reassign as the post author. Use wp_get_users to discover available author IDs.
post_parentNoParent post ID (0 = no parent). Useful for hierarchical CPTs. Throws if the ID does not exist.
comment_statusNoAllow (open) or disallow (closed) new comments.
featured_mediaNoAttachment ID to set as featured image (pass 0 to remove)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare destructive/idempotent/openWorld flags; the description adds real behavior: the response includes saved_fields read back from the DB so silent drops or silent modification surface, backslashes are stored as sent, apply happens only after human approval in Royally. That is substantive context an agent cannot get from the annotation block.

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?

Purpose is front-loaded, but the body becomes a run-on that chains unrelated topics (backslashes, masking, site name, approval workflow) with heavy parentheticals. Every claim is useful, yet the structure makes it harder to scan than a short bulleted ordering would.

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

Completeness4/5

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

For a 14-parameter destructive mutation tool with no output schema, the description covers response shape (saved_fields), write hazards, and the approval gate. It does not state whether omitted parameters leave existing values unchanged, which matters for a partial-update tool.

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

Parameters4/5

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

With 71% schema coverage the schema already documents most fields, but the description adds meaning it does not: the masking/read_is_masked hazard for content, title and excerpt, and the backslash-preservation rule for JSON unicode escapes and Divi bindings. Those are non-obvious semantics that change how the agent uses those parameters.

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?

Opens with a specific verb+resource and scope: 'Update existing post (any post type)', which separates it from wp_create_post and wp_update_post_meta. It does not explicitly state how it relates to the closely-named wp_update_page sibling, so a 4 rather than a 5.

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

Usage Guidelines4/5

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

Gives concrete conditional guidance: 'Pass date to reschedule or backdate', and routes masked/partially-hidden content to wp_replace_in_post with the caveat that its find text may not touch the hidden part. It also discloses the Royally approval gate. It stops short of naming when to prefer wp_update_page or wp_update_block_attributes over this.

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