Skip to main content
Glama
Sign In
wpxmcp

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update a navigation menu

update_menu

Rename a WordPress menu or change which theme locations it fills. Adjust display name and location assignments to keep navigation organized.

Instructions

Rename a menu or change which theme locations it fills.

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": "update_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe item ID.
nameNoDisplay name.
site_idNoWhich configured WordPress site to act on. Optional — with a single site configured it is used automatically; with several, the default site is used unless you name one. Run list_sites for valid ids.
auto_addNoAutomatically add new top-level pages to this menu.
locationsNoReplaces the current location assignments.
descriptionNoLonger descriptive text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / id / minimum
      Added value: +-9007199254740991
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

Annotations already establish it is a write operation (readOnlyHint=false) and not idempotent. The description adds no behavioral detail beyond the basic purpose—it does not disclose that changing locations replaces existing assignments (though the schema does), nor any side effects, reversibility, or permission requirements. Given annotations are present, the description's contribution is minimal.

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?

The description is a single, front-loaded sentence with zero redundant words. It captures the core actions efficiently and is appropriately sized for a tool with a clear, narrow purpose.

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?

Given the tool has six parameters, one required, and no output schema, the description is minimal but not entirely inadequate. It omits any mention of prerequisites (e.g., that the menu must already exist), site selection behavior, or what happens to unspecified fields. However, the schema covers parameter semantics, so the description is acceptable but could benefit from a note on usage scope.

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 the schema documents all six parameters. The description highlights 'name' and 'locations' as the key updatable fields but adds no additional meaning for auto_add, description, or site_id beyond what the schema provides. It meets the baseline without adding significant value.

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?

The description states a specific verb-resource pair ('Rename a menu' or 'change which theme locations it fills'), clearly distinguishing this from sibling menu tools like create_menu, delete_menu, add_menu_item, and update_menu_item. It precisely names the two primary operations, leaving no ambiguity about the tool's scope.

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?

The description implies when to use the tool (when renaming or changing menu locations) but provides no explicit guidance on when not to use it or alternatives. It does not mention that adding/removing items belongs to add_menu_item/delete_menu_item, nor any prerequisites like the menu existing. The usage context is only implied, not stated.

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