Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wp_delete_widget

Destructive

Removes a text, custom_html, or block widget from its sidebar, retaining its settings for recovery with wp_move_widget. Ask the user for confirmation first and only call with confirm=true after approval.

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>",
      "widget_id": "<widget_id>",
      "confirm": "<confirm>"
    },
    "name": "wp_delete_widget"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true only after the user explicitly confirms deletion.
site_idYesThe connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.
widget_idYesThe widget instance ID to delete.

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 openWorldHint=true, so the safety profile is known. The description adds genuinely new behavior: settings are retained after removal and recoverable via wp_move_widget, plus a required human-approval gate. It stops short of stating what happens to the sidebar layout or what a failed delete returns.

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, no filler. The action and scope come first, then the recovery note, then the confirmation requirement — ordered exactly as an agent needs to act on them.

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 destructive tool with full schema coverage and no output schema, the description covers action, scope, recoverability, and the approval gate. Only minor gaps remain, such as error behavior when the widget_id is invalid or already deleted.

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, widget_id, and confirm are already documented, including the 'must be true only after explicit confirmation' note. The description's confirm guidance largely restates the schema, adding no new syntax or format detail; baseline 3 applies when the schema does the heavy lifting.

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 ('Removes a ... widget from its sidebar') and scopes the target types to text, custom_html, or block widgets. That scope plus the recovery pointer to wp_move_widget lets an agent distinguish this from the many other wp_delete_* siblings without opening a schema.

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 clear precondition chain: ask the user, then call with confirm=true only after approval, and points to wp_move_widget if the settings need restoring. It does not explicitly name when to prefer wp_update_widget or wp_set_widget_visibility over deletion, but the decision context for a destructive call is well covered.

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