Skip to main content
Glama
RaheesAhmed

WordPress MCP Server

by RaheesAhmed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wordpress_delete_reusable_block

wordpress_delete_reusable_block

Delete a reusable block from your WordPress site by providing its block ID and specifying whether to force deletion.

Instructions

Delete a reusable block

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
blockIdYes
forceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

C2.5/5.0
Behavior1/5

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

With no annotations, the description is the sole source of behavioral disclosure, but it merely restates the tool's purpose. It does not mention that deletion is destructive and likely permanent, nor the role of the 'force' parameter.

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

Conciseness3/5

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

The description is extremely short with zero unnecessary words, but it is under-specified. It is a single sentence that could have been expanded with critical details while maintaining conciseness.

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?

The tool deletes a reusable block with no output schema or annotations, and the description does not cover the effect of the operation, the significance of the force parameter, or any safety considerations. Incomplete for a destructive operation.

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

Parameters1/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 the two required parameters (blockId, force). Without additional info, the agent cannot understand the force flag's semantics.

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 ('Delete') and resource ('reusable block'), clearly distinguishing it from sibling delete tools for posts, pages, media, etc. It fully states the tool's function.

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?

No guidance is provided on when to use this tool, when not to use it, or alternatives. It lacks information about prerequisites like the force parameter or whether blocks need to be trashed first.

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

Deploy Server

Other Tools