Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Shopify store menu

shopify_store_menu_get
Read-onlyIdempotent

Retrieve a Shopify store's navigation menu, including nested items, by providing the store domain and menu handle to inspect or reuse its structure.

Instructions

Get one of a Shopify store's navigation menus, including nested items. Requires handle and store.

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": {
      "handle": "<handle>",
      "store": "<store>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "shopify_store_menu_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeYesRequired. The store's domain, for example `allbirds.com`, `www.allbirds.com` or `weareallbirds.myshopify.com`. A full URL is accepted and reduced to its host. Only public storefront hosts are accepted.
handleYesRequired. The menu handle, as it appears in its URL, e.g. `main-menu`.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds only one behavioral fact beyond that: nested items are returned inline. It says nothing about what happens when the handle does not exist or about rate limits.

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?

Two short sentences, front-loaded with the resource and its scope, with zero filler. The second sentence largely restates required fields already visible in the schema, so it is not fully wasteful but not fully earning its place either.

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 simple idempotent read with full schema coverage and rich safety annotations, most of what an agent needs is present, but with no output schema the description carries the burden of describing the return shape and only mentions nested items in passing. Missing are the not-found behavior and any hint at the response structure.

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 every parameter, including the analytics and conversation_id conventions, is already documented in the schema, which sets the baseline at 3. The description's 'Requires `handle` and `store`' actually understates the schema's four required parameters (context and llm_model are also required), which is a mild but real loss of precision rather than added meaning.

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 states a specific verb and resource ('Get one of a Shopify store's navigation menus') and adds the notable scope detail that nested items are included. It does not name or distinguish itself from any sibling (e.g. shopify_page_get or shopify_collections_list), so it lands just short of a 5.

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?

There is no guidance on when to choose this tool over the many other store-resource getters in the sibling list, and no stated preconditions or exclusions. The single-menu framing implicitly narrows usage ('one of'), but the agent gets no routing help.

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