Skip to main content
Glama
Sign In
wpxmcp

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get a menu with its items

get_menu
Read-only

Fetch a navigation menu with all items rendered as an indented tree, clarifying the menu's hierarchy at a glance.

Instructions

Get one navigation menu together with all of its items, rendered as an indented tree so the hierarchy is obvious.

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": {
      "id": "<id>"
    },
    "name": "get_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe menu ID from list_menus.
site_idNoWhich configured WordPress site to act on. Optional — with a single site configured it is used automatically; with several, the default site is used unless you name one. Run list_sites for valid ids.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / id / minimum
      Added value: +-9007199254740991
  2. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the description doesn't need to repeat that. However, it adds the trait of returning an indented tree, which is useful. But it doesn't mention output format details, pagination, or whether items include metadata, and with no output schema, the description could provide more behavioral context.

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 sentence, concise and front-loaded with the core action. Every word earns its place — no fluff.

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 read-only retrieval tool with 2 parameters and no output schema, the description is decent but leaves gaps: it doesn't explain what happens if the menu id doesn't exist, how failures are handled, or the exact tree format. Given the sibling tools and context, it's adequate but not complete enough to anticipate edge cases.

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?

Schema description coverage is 100%, so both id and site_id are well-described in the schema. The description adds the indented tree rendering which relates to the purpose, not to specific parameters, so it doesn't add much parameter-specific value beyond the schema.

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 clearly states the purpose: retrieve one navigation menu and its items, rendered as an indented tree. It distinguishes from list_menus (which lists menus) and menu item tools, though it doesn't explicitly name alternatives.

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?

The description implies usage when you need a specific menu's hierarchy, but does not explicitly say when to use this versus other menu-related tools. It assumes the agent will infer from context, which is adequate but not stellar.

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