Skip to main content
Glama
alex-brecher

shopify-multi-store

by alex-brecher
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

shopify_create_product

Destructive

Create a Shopify product with options, variants, and images, optionally adding it to a collection. Defaults to draft and dry-run preview before applying changes.

Instructions

Create a product with options, variants and images, and optionally add it to a manual collection. Defaults to status DRAFT and to dryRun:true, which previews the input without creating anything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNo
priceNo
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.
imagesNo
statusNoDRAFT
vendorNo
optionsNo
variantsNo
productTypeNo
collectionIdNo
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 / images / items / 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

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is partly covered. The description adds genuinely important context the annotations do not convey: the dryRun:true default previews input without creating anything, and the default status is DRAFT. That is meaningful behavioral disclosure for a mutation tool, though it stops short of describing auth requirements or read-back 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?

Two tight sentences with no waste. The core action is front-loaded and the crucial default behaviors follow immediately.

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 13-parameter mutation tool with no output schema and near-zero schema descriptions, the definition should do more. The dryRun/status defaults are well covered, but most parameter semantics and any output/read-back expectation are left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 8%, so the description must compensate for 13 mostly-undocumented parameters. It names the concepts (options, variants, images, collection, defaults) but adds little meaning beyond the field names and does not explain tags, price, store, vendor, productType, collectionId format, or descriptionHtml.

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 verb+resource ("Create a product") and scopes exactly what the tool assembles: options, variants, images, and an optional manual-collection add. The verb cleanly separates it from the sibling update_product, so an agent can identify it without opening the schema.

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 explicit when-to-use guidance, no exclusions, and no mention of alternatives such as update_product or create_collection. The 'add it to a manual collection' clause even raises a question (when to use this vs create_collection) that the description never resolves.

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