Skip to main content
Glama
alex-brecher

shopify-multi-store

by alex-brecher
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

shopify_create_collection

Destructive

Create a manual or smart collection in a Shopify store, preview changes with dry-run by default, and optionally publish to selected sales channels.

Instructions

Create a manual collection (optional productIds) or a smart collection (ruleSet). Pass publicationIds to publish to explicitly selected channels. Defaults to dryRun:true, which previews the input without creating anything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imageNo
storeYes
titleYes
dryRunNoTrue (the default) returns a before/after preview without changing anything in Shopify. Pass false, after the user authorizes this store and exact change, to apply it; the tool then reads the result back.
ruleSetNo
sortOrderNo
productIdsNo
publicationIdsNo
descriptionHtmlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.1
    • removedInput schema / properties / confirm
      Removed value: -{
-  "const": true,
-  "description": "True only after authorization for this store and exact change.",
-  "type": "boolean"
-}
    • addedInput schema / properties / dryRun
      Added value: +{
+  "default": true,
+  "description": "True (the default) returns a before/after preview without changing anything in Shopify. Pass false, after the user authorizes this store and exact change, to apply it; the tool then reads the result back.",
+  "type": "boolean"
+}
    • changedInput schema / properties / image / properties / url / format
      Previous value: -"uri"New value: +"starts_with"
    • changedInput schema / required
      Previous value: -[
-  "store",
-  "title",
-  "confirm"
-]New value: +[
+  "store",
+  "title"
+]
  2. Addedv1.6.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is partly covered. The description adds the important non-obvious trait that dryRun defaults to true and previews without creating anything, though this largely restates the schema's dryRun description rather than adding new depth (no mention of auth requirements or rate/quantity limits).

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 dense sentences, front-loaded with the core mode distinction and ending on the highest-risk behavior (dryRun default). No filler; every clause carries actionable information.

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 mutation with no output schema, the description covers the key modes, publishing, and the dry-run default, and even notes that a non-dry-run call reads the result back. It stops short of enumerating required fields (store, title) or the sortOrder/descriptionHtml options, leaving minor gaps against a 9-parameter nested schema.

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 only 11% across 9 parameters, so the description must compensate, and it only covers productIds, ruleSet, publicationIds and dryRun. The mode-based semantics (manual vs smart) are genuinely useful, but image, sortOrder, descriptionHtml, store and title receive no interpretive guidance beyond their raw schema types.

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?

States a specific verb and resource ('Create a ... collection') and immediately distinguishes its two creation modes: manual (productIds) vs smart (ruleSet). An agent can tell this apart from shopify_update_collection without opening either schema.

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

Usage Guidelines3/5

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

It maps parameters to intent ('Pass publicationIds to publish to explicitly selected channels'), which implies when to use each field, but it never states when to prefer a manual vs smart collection beyond the parameter, and gives no exclusions or routing against update_collection. Usage is implied rather than prescribed.

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