Skip to main content
Glama

wp_update_post

Updates a WordPress post's title, content, or excerpt and leaves publishing to a human in wp-admin; requires write mode.

Instructions

Update a WordPress post's title, content or excerpt. Cannot publish; publishing is done by a human in wp-admin. Requires write mode.

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": "wp_update_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
titleNo
contentNo
excerptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose two valuable traits: the tool is a mutation gated behind write mode, and it deliberately cannot change publish status. It leaves unstated whether omitted fields are preserved or cleared, whether revisions are created, and what happens on an invalid id.

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?

Three short sentences with the core action first, followed by the constraint and the prerequisite. No filler, no restatement of the name, and every sentence adds information an agent needs.

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 simple four-parameter mutation with no output schema, but the description omits the single required parameter (id) and says nothing about partial-update behavior or failure modes. For a write tool with zero annotations, that leaves too much of the calling contract to inference.

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 description coverage is 0%, so the description must compensate; it names three of the four parameters (title, content, excerpt) and implicitly frames them as the only editable fields. The required 'id' parameter is never mentioned, and no format or partial-update semantics are given for any field.

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 ('Update') and resource ('a WordPress post') and enumerates the mutable fields (title, content, excerpt), which distinguishes it clearly from wp_create_post and wp_trash_post. It does not explicitly name a sibling, so it stops short of 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 an explicit when-not ('Cannot publish; publishing is done by a human in wp-admin') and a prerequisite ('Requires write mode'), which is real routing guidance. It does not say when to prefer wp_create_post for new posts or how to handle a nonexistent id, so no exclusion set is complete.

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