Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: List menu items

wordpress_list_menu_items
Read-only

Lists all items in a specific WordPress menu, returning a hierarchical view with links and ordering so you can inspect menu structure.

Instructions

[UNIFIED] List all items in a specific menu. Returns hierarchical list of menu items with links and ordering.

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>",
      "menu_id": "<menu_id>"
    },
    "name": "wordpress_list_menu_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
menu_idYes

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

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine behavioral value by describing the return as a hierarchical list with links and ordering, but it omits pagination behavior, ordering guarantees, error handling for invalid menu_id, and maximum depth.

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 that front-load the action and then the return shape. The bracketed '[UNIFIED]' tag is the only wasted token; nothing else could be trimmed without losing content.

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?

For a simple read-only listing tool with only two parameters this is close to adequate, but with 0% schema coverage and no output schema the description should at minimum explain the site parameter and how to obtain a menu_id. The return-value sentence partially compensates for the missing output schema.

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% and the two parameters (site, menu_id) are undocumented. The description hints that menu_id selects the menu but says nothing about what 'site' means (URL, slug, ID?) or where a valid menu_id comes from, leaving half the parameter surface ambiguous.

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 states a specific verb and resource: 'List all items in a specific menu', which is distinguishable from listing menus themselves or getting a single menu. However, it does not name any sibling such as wordpress_list_menus or wordpress_get_menu, and the '[UNIFIED]' prefix adds no discriminating information.

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?

There is no explicit guidance on when to use this tool versus wordpress_get_menu, wordpress_list_menus, or the wordpress_specialist_wp_menu_list variant. Usage is only implied by the phrase 'in a specific menu', which presupposes the caller already has a menu_id.

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