Skip to main content
Glama
Sign In
mcp-wordpress

mcp-wordpress

by leonardobora
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wp_get_menu

Get a WordPress classic menu by its ID or slug, returning the menu data for editing or site management.

Instructions

Get a classic menu by ID or slug.

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": {
      "ref": "<ref>"
    },
    "name": "wp_get_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. 'Get' communicates a read-only retrieval, but the description does not disclose return shape, not-found behavior, or any other runtime details that an agent could expect.

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?

One short sentence, front-loaded with the action, resource, and parameter meaning. Every word contributes and nothing is redundant.

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?

The tool is simple (one required parameter, no nested objects), so the description covers selection and invocation fully. With no output schema, it would be slightly stronger if it stated the return object shape, but the operation is a straightforward getter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only exposes a bare 'ref' as integer or string with no description. The description fully compensates by clarifying that this value is the menu ID or slug, which is exactly the missing semantic.

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 has a specific verb ('Get'), a specific resource ('classic menu'), and the supported identifiers ('by ID or slug'). It clearly marks this as the single-menu getter rather than wp_list_menus or wp_get_menu_item.

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 when to use this tool: to retrieve one classic menu when an ID or slug is known. However, it never explicitly states exclusions or names alternatives such as wp_list_menus for listing menus or wp_get_menu_item for menu items.

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