Skip to main content
Glama

shopify_update_product

Destructive

Update a product's fields, variants, media, and tags in a selected Shopify store, previewing changes by default with a dry run before anything is applied.

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "store": "<store>",
      "id": "<id>"
    },
    "name": "shopify_update_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
seoNo
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.
handleNo
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
collectionsToJoinNo
redirectNewHandleNoWith handle: add a redirect from the old URL.
collectionsToLeaveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv2.2.0
    • addedInput schema / properties / collectionsToJoin
      Added value: +{
      +  "items": {
      +    "pattern": "^gid:\\/\\/shopify\\/Collection\\/[0-9]+$",
      +    "type": "string"
      +  },
      +  "maxItems": 250,
      +  "type": "array"
      +}
    • addedInput schema / properties / collectionsToLeave
      Added value: +{
      +  "items": {
      +    "pattern": "^gid:\\/\\/shopify\\/Collection\\/[0-9]+$",
      +    "type": "string"
      +  },
      +  "maxItems": 250,
      +  "type": "array"
      +}
    • addedInput schema / properties / handle
      Added value: +{
      +  "maxLength": 255,
      +  "pattern": "^[a-z0-9][a-z0-9-]*$",
      +  "type": "string"
      +}
    • addedInput schema / properties / redirectNewHandle
      Added value: +{
      +  "description": "With handle: add a redirect from the old URL.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / seo
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "description": {
      +      "maxLength": 320,
      +      "type": "string"
      +    },
      +    "title": {
      +      "maxLength": 255,
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. 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"
      +]
  3. Addedv1.6.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is partially carried by structured data. The description adds genuine value by disclosing the dryRun default preview, the before/after return, and that ARCHIVED/DRAFT removes the product from every sales channel. It omits what a full tag replacement destroys in irreversible terms and says nothing about required scopes or authorization beyond the schema's note.

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?

Four tight sentences, front-loaded with what the tool touches, then behavior, then tag semantics, then the status consequence. Nearly every sentence earns its place, though the dryRun sentence duplicates schema wording and the tag sentence could be compressed.

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 19-parameter destructive mutation with no output schema, the description covers the highest-stakes behaviors (preview mode, tag replacement, archiving visibility) but leaves most parameters unexplained and gives no authorization or rate-limit context. An agent could call it correctly for the common cases but would be guessing on handle, collections, and media semantics.

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 26% across 19 parameters, so the description must compensate and it only partially does — it clarifies dryRun, the three tag parameters, and status. Parameters such as handle/redirectNewHandle, collectionsToJoin/Leave, removeMediaIds, images, variants, seo, and descriptionHtml are mentioned only obliquely ('media') or not at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ('Update product fields, variants, media and tags'), immediately conveying scope. It does not explicitly distinguish itself from siblings like shopify_update_collection or shopify_create_product, but the product focus is unambiguous from the name plus opening sentence.

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 explains the dryRun preview-vs-apply workflow, which is real usage guidance, but never states when to choose this tool over alternatives such as shopify_manage or raw GraphQL mutations. The tag guidance ('replaceTags replaces all tags') implies caution but does not explicitly say to prefer addTags/removeTags, though the schema descriptions do.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.