Skip to main content
Glama
cvrt-jh

wordpress-mcp

by cvrt-jh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mcp_get_menu_locations

Retrieve all registered menu locations for a WordPress site using its site ID, so you can see where menus can be assigned.

Instructions

Get registered menu locations

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.4.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / site
      Added value: +{
+  "description": "Site id (see list_sites)",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "site"
+]
  2. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden. 'Get' implies a read-only retrieval, but the description does not state permissions, side effects, return shape, or what 'registered' means in this context.

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?

The description is a single front-loaded sentence with no wasted words. It is concise, though extremely minimal for a tool whose relationship to menu assignment could be briefly contextualized.

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?

The tool is simple with one required parameter and no output schema or annotations. The description states what is returned in general terms, but does not clarify the return format or how these locations relate to assigning menus.

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 coverage is 100%, and the sole parameter 'site' is documented as 'Site id (see list_sites).' The description adds no parameter meaning, so the schema already does the work; baseline 3 applies.

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 gives a specific verb and resource: 'Get registered menu locations.' It is distinguishable from sibling tools like mcp_list_menus (menus themselves) and mcp_assign_menu_location (assignment), though it does not explicitly name or contrast those siblings.

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?

The description offers no when-to-use guidance, no prerequisites, and no alternatives. It does not explain when an agent should call this versus mcp_list_menus or mcp_assign_menu_location.

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