Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp menu list

wordpress_specialist_wp_menu_list
Read-only

Lists WordPress navigation menus with IDs, names, slugs, assigned theme locations, and item counts so you can find the menu_id needed for menu retrieval or updates.

Instructions

[UNIFIED] List every WordPress nav-menu with id / name / slug, the theme locations bound to it, and the item count. Use to discover menu_id before calling wp_menu_get / wp_menu_set. Requires Airano MCP Bridge v2.17.0+ and manage_options.

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_specialist_wp_menu_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds real value on top: the exact fields returned and the bridge version plus capability requirement. It stops short of describing pagination or behavior on sites with many menus, but nothing contradicts the read-only annotation.

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?

Two sentences, no filler. The output fields and the call-sequencing pointer come first, and the environment prerequisites come last, which is the right order for an agent scanning the definition.

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 simple read-only list tool with no output schema, the description covers what it returns, why to call it, and what it requires to run. Only the semantics of the "site" argument are left unexplained, which is a modest but real omission.

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?

The single parameter "site" has 0% schema description coverage, so the description carries the full burden here — but it never says whether site is an alias, ID, domain, or URL. That ambiguity is the one gap that could cause a mis-invocation.

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 names a specific verb and resource ("List every WordPress nav-menu") and enumerates exactly what is returned: id / name / slug, bound theme locations, and item count. That detail distinguishes it cleanly from wp_menu_get (single menu) and wp_menu_set (mutation).

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

Usage Guidelines5/5

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

It states the concrete use case ("discover menu_id before calling wp_menu_get / wp_menu_set"), which tells the agent both when to call this and which siblings to route to afterwards. It also gives hard prerequisites (Airano MCP Bridge v2.17.0+ and manage_options), so an agent knows when the call will fail.

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