Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wp_delete_menu

Destructive

Deletes a navigation menu. 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>",
      "id": "<id>",
      "confirm": "<confirm>"
    },
    "name": "wp_delete_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe menu term ID to delete.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's main added value is the consent workflow, which is useful. It never says what actually gets destroyed alongside the menu (contained menu items, location assignments) or whether the deletion is permanent, which is the key unknown for a destructive operation.

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 action and immediately followed by the safety gate. No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter destructive tool the essentials are covered: what it deletes, the required confirmation, and the schema's site_id guidance. Gaps remain around cascade effects and irreversibility, which matter because no output schema exists to reveal the result of the operation.

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%, with site_id, id, and confirm each documented in the schema, including the list_sites prerequisite. The description only restates the confirm semantics already spelled out in the schema and adds no new meaning for id or site_id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Deletes a navigation menu" gives a specific verb and resource, so the operation is unambiguous. It does not differentiate itself from the near-identical sibling wp_delete_navigation_menu, leaving the agent to guess which one applies to the target entity.

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 states an explicit precondition: obtain user confirmation and only then pass confirm=true. That is real when-to-use guidance rather than implied usage. It stops short of naming an alternative or stating when not to use this tool at all.

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