Skip to main content
Glama
alex-brecher

shopify-multi-store

by alex-brecher
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

shopify_update_product

Destructive

Update Shopify product fields, variants, media, and tags. Preview changes with dryRun before applying them to a store.

Instructions

Update product fields, variants, media and tags. dryRun:true (the default) returns the current product and the change without applying it; dryRun:false applies it and returns before and after. Tags: addTags and removeTags change only the named tags; replaceTags replaces all tags. A status of ARCHIVED or DRAFT takes the product off every sales channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
storeYes
titleNo
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
statusNo
vendorNo
addTagsNoTags to add (tagsAdd). Other tags are kept.
variantsNo
removeTagsNoTags to remove (tagsRemove). Other tags are kept.
productTypeNo
replaceTagsNoReplaces all tags: every current tag not in this list is removed. Prefer addTags or removeTags.
removeMediaIdsNo
descriptionHtmlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.0.1
    • addedInput schema / properties / addTags
      Added value: +{
+  "description": "Tags to add (tagsAdd). Other tags are kept.",
+  "items": {
+    "maxLength": 255,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 250,
+  "type": "array"
+}
    • 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"
    • addedInput schema / properties / removeTags
      Added value: +{
+  "description": "Tags to remove (tagsRemove). Other tags are kept.",
+  "items": {
+    "maxLength": 255,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 250,
+  "type": "array"
+}
    • addedInput schema / properties / replaceTags
      Added value: +{
+  "description": "Replaces all tags: every current tag not in this list is removed. Prefer addTags or removeTags.",
+  "items": {
+    "maxLength": 255,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 250,
+  "type": "array"
+}
    • removedInput schema / properties / tags
      Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "maxItems": 250,
-  "type": "array"
-}
    • changedInput schema / required
      Previous value: -[
-  "store",
-  "id",
-  "confirm"
-]New value: +[
+  "store",
+  "id"
+]
  2. Addedv1.6.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint and openWorldHint, but the description adds real consequence detail: dryRun previews by default and returns before/after on apply, and a status of ARCHIVED/DRAFT removes the product from every sales channel. It adds meaningful context but omits auth/permission and rate-limit behavior.

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?

Front-loaded with the core purpose, then compact sentences for dryRun, tag semantics, and status side effects. Every sentence carries information, though the tag explanation is slightly dense.

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 destructive 14-parameter mutation with no output schema, the description covers the highest-stakes behaviors (preview workflow, tag add/remove/replace, status effects) and return values. The remaining gap is the many field parameters that get no semantic explanation.

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?

With only 29% schema description coverage, the description must carry more weight, and it only clarifies dryRun, the three tag parameters, and status. Many of the 14 parameters (id, store, images, vendor, variants, productType, descriptionHtml, removeMediaIds) are left to the schema with no added meaning.

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 (Update) and resource (product) plus the surface scope: fields, variants, media, tags. This clearly separates it from the sibling shopify_create_product and the other update_* tools without needing to open a schema.

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?

Gives clear operational context: dryRun defaults to true for a preview and must be set false only after the user authorizes the exact change. It does not name alternative tools or explicit when-not-to-use conditions, so it stops short of full 5-level guidance.

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