Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wp_delete_block

Destructive

Deletes a Gutenberg block from a post. Ask the user for confirmation first and only call this tool with confirm=true after they approve.

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": {
      "site_id": "<site_id>",
      "post_id": "<post_id>",
      "confirm": "<confirm>"
    },
    "name": "wp_delete_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoRaw block-tree path returned by wp_list_blocks. Use this for nested blocks.
indexNoZero-based block index to delete.
confirmYesMust be true only after the user explicitly confirms deletion.
post_idYesThe post ID containing the block.
site_idYesThe connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is known. The description adds real context beyond that: a mandatory human-confirmation protocol before invocation. It omits what happens to nested child blocks and whether deletion is recoverable, which prevents a 5.

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 short sentences, front-loaded with the action and immediately followed by the safety precondition. Nothing is wasted or buried.

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?

Covers the highest-risk aspect (irreversible deletion requiring confirmation) for a 5-parameter destructive tool with no output schema. Minor gaps remain around nested-block cascade behavior and recoverability, which matter for a block-tree tool exposing a path parameter.

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 100%, so site_id, post_id, index, and path are all documented in the schema. The description only reinforces the confirm parameter's semantics, adding no new meaning about path vs. index precedence. Baseline 3 applies.

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?

States a specific verb and resource: 'Deletes a Gutenberg block from a post.' This cleanly separates it from wp_delete_post (whole post) and wp_update_block/wp_move_block, and the scope of a single block is unambiguous.

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 a firm gating rule: ask the user for confirmation first and only call with confirm=true after approval. That is clear guidance on when it is permissible to invoke. It does not name alternatives (e.g., wp_update_block to rewrite content instead of deleting), which keeps it from a 5.

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

All Frontman for WordPress toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources