Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Create menu

wordpress_create_menu
Destructive

Creates a new WordPress navigation menu for a site and optionally assigns it to theme locations, so you can set up site navigation structure.

Instructions

[UNIFIED] Create a new navigation menu. Can optionally assign to theme locations.

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": "<site>",
      "name": "<name>"
    },
    "name": "wordpress_create_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
siteYes
slugNo
locationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv3.4.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false, which is consistent with the create wording. The description adds no behavioral context beyond that — it doesn't explain why a create operation is flagged destructive (e.g., whether assigning locations replaces an existing menu there), nor permission requirements or what happens on duplicate names. With the safety profile already in annotations, the description contributes almost nothing extra.

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?

Two short sentences with the primary action front-loaded and no filler. The '[UNIFIED]' marker is the only wasted token, and the optional-location note is placed logically after the main action.

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?

For a mutation tool with a destructive annotation, no output schema, and zero schema coverage on four parameters, the description is too thin. An agent learns what it creates but not what it returns (menu ID?), what permissions or site scoping are required, or how location assignment interacts with existing assignments.

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 0% across 4 parameters, so the description must carry the load. It only gestures at two of them: the menu name and the optional theme locations. The required 'site' parameter and the 'slug' parameter are entirely unexplained, leaving half the inputs ambiguous for an agent.

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 gives a specific verb and resource: 'Create a new navigation menu.' This is distinguishable from siblings like wordpress_create_menu_item and wordpress_get_menu. The unexplained '[UNIFIED]' prefix adds noise rather than meaning, but the core purpose is unambiguous.

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 on when to create a menu versus when to look one up with wordpress_get_menu or add entries with wordpress_create_menu_item. The mention that it 'Can optionally assign to theme locations' describes a capability rather than a usage condition, and no prerequisites or ordering constraints (e.g., menu must exist before adding items) are given.

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