Skip to main content
Glama

shopify_create_collection

DestructiveIdempotent

Create a Shopify collection and publish it to the Online Store, optionally adding products by ID.

Instructions

Create a custom Shopify collection (optionally seeded with products) and publish it to the Online Store sales channel. Use to group sellables into a browsable storefront category.

Args:
    title (required): Collection title.
    description_html: Collection description (HTML allowed).
    handle: URL handle (defaults to a slug of the title).
    product_ids: Product IDs (numeric or GIDs) to add on creation.
    publish: Publish to the Online Store channel after creation (default true).
    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
titleNo
effectNo
handleNo
publishNo
project_idNo
product_idsNo
project_refNo
approval_refNo
idempotency_keyNo
description_htmlNo
connector_account_refNo

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
Behavior4/5

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

Annotations already establish readOnly=false and destructiveHint=true, lowering the burden. The description adds meaningful context by disclosing the public storefront publishing side effect and the optional product-seeding behavior, plus the default publish=true behavior.

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?

The purpose is front-loaded in two clear sentences, followed by a compact Args list where each line provides distinct value. With 11 parameters and zero schema-level descriptions, this length is justified rather than wordy.

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?

The description covers the operation, all parameters, defaults, the publishing side effect, and idempotency/approval context, and an output schema exists so return-value documentation is not needed. It misses only minor routing guidance such as when to prefer a non-published or automated collection, keeping it just below a 5.

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 description coverage is 0%, and the Args block compensates well by explaining every parameter: handle defaulting, product ID types, publish default, project correlation refs, idempotency, effect verification, and approval ref semantics. It loses a point because it calls title required while the schema allows null and lists no required properties.

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 states a specific action ('Create a custom Shopify collection'), scopes it (optionally seeded with products), and names the key side effect (publish to Online Store). This clearly distinguishes it from sibling tools like shopify_update_collection or shopify_list_collections.

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 provides an explicit use context ('Use to group sellables into a browsable storefront category'), which tells an agent when this tool is appropriate. It does not name alternative tools or give when-not-to-use conditions, but the create/update/list sibling split is otherwise clear.

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