Skip to main content
Glama
Sign In
mcp-wordpress

mcp-wordpress

by leonardobora
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wp_delete_menu_item

Permanently remove a WordPress classic menu item by its ID, with an optional dry-run to preview changes before deletion.

Instructions

Permanently delete a classic menu item.

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": {
      "id": "<id>"
    },
    "name": "wp_delete_menu_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
forceNo
dry_runNoPreview changes without writing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the burden of disclosing destructive behavior. 'Permanently delete' conveys irreversibility, which is useful, but it omits other behavioral context such as auth requirements, effects on related data, or confirmation behavior.

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?

A single, front-loaded sentence with no filler. Every word adds meaning: 'Permanently' signals irreversibility, 'delete' the action, and 'classic menu item' the target resource.

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

Completeness2/5

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

The tool is destructive, has 3 parameters, no annotations, and no output schema. The description is too sparse to fully support correct invocation; it does not mention how to use dry_run, what confirms success, or any prerequisites.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%. The description adds no meaning for the required 'id' parameter or the 'force' parameter, and the only parameter with a schema description is 'dry_run'. The description does not compensate for the low coverage.

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 states a clear verb and resource: 'Permanently delete a classic menu item.' It distinguishes the tool from wp_delete_menu by specifying it deletes an item rather than a whole menu, though it does not explicitly name that sibling.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool versus wp_update_menu_item, wp_get_menu_item, or wp_delete_menu. The intended context is only implied by the verb 'delete'.

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

Deploy Server

Other Tools