Skip to main content
Glama

royal-mcp__wp_update_page

Destructive

Update existing page. 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. The reply carries an undo token that puts back the fields this call changed; a template change has its own token (template_undo_token). 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_page, 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_page"
  }
}

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 page excerpt. May contain safe HTML.
site_idNoSite to run this tool on: 8ef2e52b-bd07-4671-a363-ebe8b480b65c (https://demo.royalplugins.com)
passwordNoPage password. Empty string removes protection.
templateNoPage template: default, or a template filename the theme offers for pages. Anything else is refused and the error lists the valid values. The reply carries template_undo_token, which restores the prior template (only the template).
menu_orderNoOrder among sibling pages. Lower = earlier in navigation.
post_authorNoUser ID to reassign as page author.
post_parentNoParent page ID (0 = top-level). Throws if the ID does not exist.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / template / description
      Previous value: -"Page template: default, or a template filename the theme offers for pages. Anything else is refused and the error lists the valid values. The reply carries an undo token that restores the prior template (only the template)."New value: +"Page template: default, or a template filename the theme offers for pages. Anything else is refused and the error lists the valid values. The reply carries template_undo_token, which restores the prior template (only the template)."
  2. 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. The reply carries an undo token that restores the prior template (only the template).",
      +  "type": "string"
      +}
  3. Added
  4. Removed
  5. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations declare a destructive, non-idempotent, open-world write; the description adds substantially beyond that: saved_fields is read back from the DB to surface silent-drop or silent-modify, undo and template_undo_token scopes are spelled out (template token restores only the template), and the Royally approval gate means nothing changes on the site until a person approves. These are exactly the side effects and reversibility facts an agent needs before a mutation.

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?

Front-loads the verb and the highest-value fact (saved_fields read-back) before the routing and undo details. The parentheticals and the site clause add density, but each sentence carries information that is not repeated in the schema or annotations.

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?

For a 12-parameter destructive mutation with no output schema, the description explains the response shape (saved_fields, undo token, template_undo_token), the approval workflow, and the one risky edge case (masked content). Nothing an agent needs to call it safely appears to be missing.

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?

Schema coverage is 67%, and the description adds real meaning for the ambiguous cases: date is ISO 8601 site-timezone and combines with status=future or backdates alone, template rejects unknown values with an error listing valid ones, and password/template undo semantics are noted. Title, status, and content remain without extra meaning beyond 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?

States a specific verb and resource ('Update existing page') and immediately distinguishes itself from wp_replace_in_page for the case of masked content. It is clear what the tool does, though the core purpose sentence itself is terse and the differentiation is buried in a later parenthetical.

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 routing rules: pass date to reschedule or backdate, and use wp_replace_in_page when a read shows masked content that must not be replaced wholesale. It does not cover when to prefer wp_update_post or other field-level siblings, so guidance is clear but not exhaustive.

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