Skip to main content
Glama

royal-mcp__wp_delete_menu

Destructive

Delete a whole navigation menu with its items. Requires edit_theme_options. The menu is removed from any theme location it was assigned to. Undo recreates the menu, its items (with their nesting and other saved item settings), its theme locations and its auto-add-pages setting; the items get new IDs. Undo refuses when a menu with the same name exists again, unless force. (site: demo.royalplugins.com) Through Royally: waits for a person to approve it in Royally; nothing on the site changes until then.

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": {
      "menu_id": "<menu_id>"
    },
    "name": "royal-mcp__wp_delete_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
menu_idYesMenu ID from wp_get_menus.
site_idNoSite to run this tool on: 8ef2e52b-bd07-4671-a363-ebe8b480b65c (https://demo.royalplugins.com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations (destructive, non-idempotent): discloses that the menu is detached from theme locations, describes exactly what undo restores (items, nesting, locations, auto-add-pages setting) and that item IDs change, and states the force-required refusal condition along with the approval-gating behavior 'nothing on the site changes until then.'

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

Conciseness4/5

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

Front-loaded with the action, then permissions, side effects, undo semantics and approval gating in compact sentences. Slightly dense with parenthetical site/approval boilerplate, but every clause carries real information.

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

Completeness5/5

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

For a destructive, approval-gated mutation with no output schema, the description covers permissions, side effects, undo behavior and its failure mode, and the human-approval delay—everything an agent needs before invoking it.

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 coverage is 100%, so menu_id and site_id are already documented; the description adds no parameter-level detail beyond what the schema supplies. 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+resource ('Delete a whole navigation menu with its items') and distinguishes from the sibling wp_delete_menu_item by emphasizing 'whole' menu plus its items.

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?

Implies use when a full menu and its items must be removed rather than a single item (contrast with wp_delete_menu_item), and states the required capability edit_theme_options. No explicit 'when not to use' or named alternative, so short of 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources