Skip to main content
Glama
Sign In
mcp-wordpress

mcp-wordpress

by leonardobora
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wp_list_menus

Retrieve classic navigation menus and their assigned theme locations to identify which menus are available and where they appear.

Instructions

List classic navigation menus and assigned theme locations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wp_list_menus"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page
orderNoasc
searchNo
orderbyNoname
per_pageNoResults per page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It conveys that the tool returns menus and their theme locations, and 'list' implies a read operation, but it does not mention pagination behavior, response shape, or any access considerations.

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 focused sentence with no filler. It front-loads the action and resource, and every word contributes to understanding what the tool does.

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?

There is no output schema and no annotations, so the description is the only source of context. It names the result categories but omits return format, pagination details, and relationship between menus and theme locations, leaving an agent underinformed for a tool with five optional parameters.

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 40%; page and per_page are documented in the schema, but order, search, and orderby are not. The description adds no parameter-level meaning and does not compensate for the undocumented parameters.

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 uses a specific verb ('List') and a specific resource ('classic navigation menus'), and adds 'assigned theme locations' to clarify scope. The word 'classic' helps distinguish this from other menu-related tools such as block-menu operations.

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?

The description gives no explicit guidance about when to use this tool versus alternatives like wp_get_menu or wp_list_menu_locations. It implies a list-style usage, but it does not state exclusions or preferred conditions.

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