Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: List menus

wordpress_list_menus
Read-only

Retrieves all WordPress navigation menus from a site, returning each menu with its assigned locations and item counts so you can inspect theme menu structure before editing.

Instructions

[UNIFIED] List all WordPress navigation menus. Returns list of menus with their locations and item counts.

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

Input Schema

NameRequiredDescriptionDefault
siteYes

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

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds useful context beyond annotations by describing what comes back (locations and item counts), which matters since no output schema exists. It says nothing about pagination, ordering, permissions, or empty-site behavior.

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 tight sentences with the action first and the return contents second; nothing is padded. The "[UNIFIED]" prefix carries no meaning for an agent but is minimal noise.

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 one-parameter read-only list tool the definition covers purpose and return contents, which is close to sufficient. The remaining gap is the undocumented required site parameter, which the description leaves to the schema and the schema does not explain.

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?

There is one parameter (site) with 0% schema description coverage and the description never mentions it, so meaning for required arguments is not compensated. The scope word "all" weakly implies no filtering arguments are needed, but the site identifier's format is left entirely to the caller.

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?

States a specific verb and resource ("List all WordPress navigation menus") and even previews the return shape (menus with locations and item counts). It does not distinguish itself from nearby siblings such as wordpress_list_menu_items or wordpress_list_navigations, so an agent could still hesitate between them.

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?

Usage is only implied by the name and the "list all" phrasing. There is no statement of when to prefer this over wordpress_list_menu_items (items within a menu) or wordpress_list_navigations, and no prerequisites or exclusions 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