Skip to main content
Glama

shopify_update_menu

DestructiveIdempotent

Update a Shopify storefront navigation menu by replacing its title, handle, and complete item tree, after verifying the current menu matches an approved digest.

Instructions

Replace a storefront navigation menu's title, handle, and full item tree. This is a whole-menu replacement — read the menu first with shopify.get_menu, approve its exact semantic preimage, and send back every item you want to keep. The connector re-reads the preimage immediately before dispatch and independently compares the complete result. Requires the online-store-navigation scopes; a connection without them returns SHOPIFY_NAVIGATION_SCOPE_REQUIRED (offer a Shopify reconnect).

Args:
    menu_id (required): Menu ID to update (numeric or GID).
    title (required): Menu title (send the existing title to keep it).
    handle (required): Menu handle (send the existing handle to keep it).
    items (required): JSON-string list of the menu's complete item tree: [{title, type?, url?, resource_id?, items?}]. Items omitted here are removed from the menu.
    expected_preimage_sha256 (required): Exact governed get_menu semantic-tree digest approved for replacement. A changed digest fails before provider dispatch.
    project_id: Authenticated Project UUID.
    project_ref: Exact project correlation reference.
    connector_account_ref: Project-bound connector account alias.
    idempotency_key: Stable business-action identity.
    effect: Claimed read or write effect; Spring verifies it.
    approval_ref: Approved platform task UUID when resuming a write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNo
titleNo
effectNo
handleNo
menu_idNo
project_idNo
project_refNo
approval_refNo
idempotency_keyNo
connector_account_refNo
expected_preimage_sha256No

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv0.1.1

TDQS

A4.4/5.0
Behavior5/5

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

The description fully discloses the destructive replacement behavior, removal of omitted items, preimage re-read and comparison before dispatch, scope requirement, idempotency key semantics, effect verification, and approval resume behavior. This significantly exceeds the annotations.

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 purpose and preconditions are front-loaded and the argument list is well organized. Some safety language is repeated across the opening paragraph and the argument descriptions, making it slightly less concise than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers all important invocation context: required scopes, error behavior, preimage digest approval, full item tree requirement, idempotency, effect verification, and approval resume. Since an output schema reportedly exists, not describing return values is acceptable.

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?

Every parameter receives a useful semantic explanation, far beyond the bare schema. However, the prose marks several arguments as required while the schema declares all optional, and it describes items as a JSON-string object list while the schema says array of strings, creating invocation-risking contradictions.

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 sentence states a precise action: replacing a storefront navigation menu's title, handle, and full item tree. It clearly distinguishes this from create/get/delete menu siblings by emphasizing whole-menu replacement and requiring an existing menu ID.

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

Usage Guidelines4/5

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

It gives a clear invocation workflow: read the menu with shopify.get_menu, approve the exact semantic preimage, submit the complete item tree, and expect removal for omitted items. It also documents the required scope and failure mode, though it does not explicitly contrast with shopify_create_menu or partial update alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RPasquale/lightbulb-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server