Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wp_delete_navigation_menu

Destructive

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

Input Schema

NameRequiredDescriptionDefault
idYesThe wp_navigation post ID.
confirmYesMust be true only after explicit confirmation.
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.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is partly covered. The description adds genuinely new behavioral context by mandating a confirmation gate before invocation, though it does not disclose whether assigned locations or child menu items are also affected, or that the deletion is irreversible.

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 with zero filler, front-loading the operation and then the confirmation constraint. Nothing is redundant.

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 destructive, irreversible mutation with no output schema, the definition covers the critical agent-facing requirement: the confirmation workflow. It is slightly incomplete on side effects — whether deleting a menu removes its items or detaches assigned locations — which matters for a destructive operation, but annotations already signal the risk.

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 all three parameters are already documented, including the confirm flag and the site_id lookup instruction. The description reinforces the confirm semantics but adds no further syntax or format detail beyond the schema; baseline 3 is appropriate.

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?

The description uses a specific verb and resource: 'Deletes a block-theme navigation menu.' The 'block-theme' qualifier hints at a distinction from the classic-menu sibling wp_delete_menu, but it never names or contrasts that sibling explicitly, so the differentiation is only implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear procedural precondition — obtain user confirmation and only pass confirm=true after approval — which is useful context. However, it offers no when-to-use guidance relative to wp_delete_menu or the other delete siblings, and no guidance on when deletion is inappropriate (e.g., menu still assigned to a location).

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