Skip to main content
Glama

update_collection

Update a Shopify collection's title, description, or URL handle. Changing the handle breaks existing links because no automatic redirect is created.

Instructions

Update an existing collection's title, description (HTML), or URL handle. Only provide fields you want to change; omitted fields are left untouched. Changing the handle changes the storefront URL — Shopify does NOT create automatic redirects from the old slug, so existing links break. To change collection membership use add_products_to_collection / remove_products_from_collection instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesGID of the collection to update.
titleNoNew display title. Omit to leave unchanged.
descriptionNoNew HTML body for the collection page. Pass an empty string to clear it.
handleNoNew URL slug. Changing a handle breaks any external links pointing at the old URL — Shopify does NOT auto-redirect.
Behavior4/5

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

Warns that changing handle breaks existing links without redirects, which is critical behavioral info. No annotations provided, so description carries full burden.

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?

Three sentences covering purpose, usage, and warning. Extremely efficient with no fluff.

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?

Covers all key aspects for an update tool: what fields, how to use, side effects. No return value explanation but acceptable given no output schema.

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?

Adds meaning beyond schema: clarifies description is HTML, handle change implications, and that empty string clears description. Schema coverage is 100% so baseline is 3.

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 clearly states it updates a collection's title, description, or handle, and distinguishes from membership-changing tools.

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?

Explicitly explains when to use (update title/desc/handle), how to use (omit unchanged fields), and points to alternative tools for membership changes.

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/miller-joe/shopify-mcp'

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