Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp menu get

wordpress_specialist_wp_menu_get
Read-only

Retrieve a WordPress navigation menu and its items by site and menu ID, including titles, types, links, parents, and order for editing or auditing menus.

Instructions

[UNIFIED] Read a single nav-menu's items. Returns {id, name, slug, items: [{id, title, type, object, object_id, parent, order, url, target, classes, xfn}]}. type is one of post_type / taxonomy / custom. 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>",
      "menu_id": "<menu_id>"
    },
    "name": "wordpress_specialist_wp_menu_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
menu_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.6/5.0
Behavior4/5

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

Beyond readOnlyHint=true, the description discloses real operational context: a minimum bridge version (v2.17.0+) and the required manage_options capability. It also documents the exact response shape, which annotations cannot convey. It stops short of describing failure modes for a missing or invalid menu_id.

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?

Three dense sentences: purpose, return contract, and prerequisites, in that order. Every clause carries information and nothing is padded.

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?

With no output schema, the description usefully takes on the return contract, and it covers auth and version prerequisites for a tool whose annotations only cover safety. The gap is parameter documentation at 0% schema coverage, which leaves the required `site` argument undefined.

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%, so the description must carry parameter meaning, and it largely does not. menu_id is loosely implied by "single nav-menu," but the `site` parameter is never explained at all (target site URL? alias? ID?), leaving an agent to guess at a required input.

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: "Read a single nav-menu's items," and enumerates the returned fields, so the agent knows exactly what comes back. It implicitly distinguishes itself from the menu list sibling by specifying a single menu, but never names that alternative.

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 implied by "single nav-menu" plus the required menu_id, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative such as the list tool for enumerating menus. An agent must infer the selection rule.

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