mcp-wordpress

wp_blocks_delete

Delete reusable blocks, sending them to trash. Optionally force permanent deletion with confirmation. Note: referencing posts display an empty placeholder.

Instructions

Delete a reusable block. Default trash. force=true with confirm="DELETE_PERMANENTLY_" hard-deletes (MODE=full). WARNING: posts/pages referencing this block will show an empty block placeholder.

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

Input Schema

Name	Required	Description	Default
`id`	Yes
`force`	No
`confirm`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations provided, the description fully discloses the destructive behavior: default trash, hard-delete requires force=true and confirm='DELETE_PERMANENTLY_<id>', and referencing posts/pages will show empty placeholders. This is comprehensive for a delete operation, including the MODE=full implementation detail.

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 three sentences, each serving a clear purpose: the action, the deletion modes, and the warning. It is front-loaded with the primary purpose and contains no unnecessary words.

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 3-parameter delete tool with no annotations and no output schema, the description adequately covers the deletion process, the confirmation requirement, and the impact on referencing content. It does not describe the return value or error cases, but these are less critical for a delete tool and the warning covers the main risk.

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?

The schema has 0% description coverage, so the description compensates by explaining the force parameter (force=true triggers hard delete) and the confirm string format. The id parameter is implied but not explicitly described, though it is obvious from the context. This adds significant value over the bare schema.

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 explicitly states "Delete a reusable block" with a specific verb and resource, clearly distinguishing it from sibling tools like wp_blocks_create, wp_blocks_get, and wp_blocks_update. It also clarifies the default trash behavior and the hard-delete option, further defining the tool's scope.

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 provides clear context on how to perform both trash (default) and permanent deletion (force=true with confirm), including the required confirmation format. It does not explicitly name alternative tools or state when to choose one deletion mode over the other, but the warning about placeholder blocks gives practical guidance for usage.

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

Deploy Server