Skip to main content
Glama

OhGiftPlease Gift Discovery

BrowseWixRESTDocsMenu

Read-only

Browse the Wix REST API documentation menu hierarchy. Alternative to SearchWixRESTDocumentation - use this to explore and discover APIs by navigating the menu structure instead of searching by keywords.

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": {
      "reason": "<reason>"
    },
    "name": "BrowseWixRESTDocsMenu"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesOne sentence describing the original user request and why you are browsing this part of the docs menu.
menuUrlNoURL of the menu to browse. Empty/omitted returns the root menu. Copy the URL from links in previous responses of this tool. Example: "https://dev.wix.com/docs/api-reference/ecommerce" or "https://dev.wix.com/docs/api-reference/ecommerce/catalog"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. Beyond that, the description discloses the key behavioral trait that responses contain links whose URLs feed back into subsequent calls, revealing the navigation loop and the stateless depth model. It stops short of describing what a menu entry or leaf response actually contains.

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?

Purpose and the alternative-tool distinction are front-loaded in the first two sentences, followed by the drill-down rules. The long bulleted list of vertical URLs is repetitive but each entry is directly usable as a menuUrl, so it earns its space; the description is somewhat longer than strictly necessary.

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?

For a two-parameter, read-only navigation tool with no output schema, the description covers purpose, alternative, depth semantics, and concrete entry points. The only thin spot is the required `reason` parameter, whose purpose is left entirely to the schema description.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it explains the omit-vs-pass semantic for menuUrl in terms of navigation depth and supplies eleven concrete example URLs for major Wix verticals, which the schema only hints at with two generic examples.

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 first line states a specific verb and resource: 'Browse the Wix REST API documentation menu hierarchy.' It then explicitly contrasts itself with a keyword-search alternative, so an agent can distinguish browsing-by-navigation from searching without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description names the alternative (keyword search) and states the condition that selects this tool ('explore and discover APIs by navigating the menu structure instead of searching'). It also gives concrete operational rules: omit menuUrl for top-level categories, pass menuUrl to drill in, and copy the URL from prior responses.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.