mcp-wordpress

wp_update_page

Update WordPress page fields by ID or slug: modify title, content, status, author, template, and more with optional dry-run preview.

Instructions

Update selected fields on a WordPress page by ID or slug.

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": {
      "ref": "<ref>"
    },
    "name": "wp_update_page"
  }
}

Input Schema

Name	Required	Description
`ref`	Yes
`slug`	No
`title`	No
`author`	No
`parent`	No
`status`	No
`content`	No
`dry_run`	No	Preview changes without writing
`excerpt`	No
`date_gmt`	No
`template`	No
`menu_order`	No
`featured_media`	No
`if_unmodified_since`	No	Fail if modified_gmt changed since this timestamp

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Sep 3, 2026

TDQS

B3.1/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. It conveys that only selected fields are changed, which is useful, but it does not mention permissions, reversibility, concurrency checks like if_unmodified_since, dry-run behavior, or what response to expect. This is a significant gap for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficiently worded sentence. It front-loads the action and resource, then adds the key identification detail without any filler or redundancy.

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

Completeness2/5

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

This is a complex tool with 14 parameters, no annotations, and no output schema, yet the description provides only a one-line overview. It does not cover required prerequisites, parameter relationships, or behavior details, so an agent would be under-informed when invoking it correctly.

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

Parameters2/5

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

Schema description coverage is only 14%, so the description must compensate for the remaining undocumented parameters. It adds meaning for 'ref' by clarifying that it can be an ID or slug, but it does not explain the other 12 parameters such as status, date_gmt, menu_order, or featured_media.

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 states a specific verb ('Update'), a clear resource ('WordPress page'), and the identification methods ('by ID or slug'). It distinguishes this tool from siblings like wp_get_page (read) and wp_update_page_content (content-only update) by indicating it updates selected fields.

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?

The description gives no guidance on when to use this tool versus alternatives such as wp_update_post, wp_update_page_content, or wp_create_page. There are no explicit conditions, exclusions, or naming of sibling tools, so an agent has to infer appropriate usage.

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

Deploy Server