mcp-wordpress

wp_blocks_update

Update reusable WordPress blocks with partial edits. Changes automatically apply to all posts and pages using the block.

Instructions

Partially update a reusable block. NOTE: editing a reusable block updates its content in every post/page that uses it.

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_blocks_update"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`slug`	No
`title`	No
`status`	No
`content`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description discloses the key side effect that changes propagate to every post/page using the block. It also communicates PATCH-like partial update behavior. It does not cover auth, return values, or reversibility, but the most significant behavioral trait is revealed.

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?

Two sentences, front-loaded with the main action and a vital caveat; no redundant filler. Efficient and easily scannable.

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 mutation tool with no output schema and no annotations, the description presents the core action and a crucial side effect. It omits details like return value or permissions, but the schema covers acceptable fields and the description gives enough context for safe invocation.

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 0% and the description does not explain any of the five parameters. It adds no meaning beyond the raw schema, failing to compensate for the low coverage; only 'partial update' implies optionality of fields.

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 uses a specific verb 'Partially update' with a clear resource ('a reusable block'), distinguishing it from sibling create/delete/get operations. It also differentiates from general post/page updates by focusing on the reusable block resource.

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?

The description implies usage for updating reusable blocks and adds critical context via the NOTE about global propagation across posts/pages. It lacks explicit alternatives or when-not-to-use guidance but provides clear contextual direction.

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

Deploy Server