Skip to main content
Glama

Update Product

sirv_update_product
DestructiveIdempotent

Update fields of a single product by sending only the values you want to change; omitted fields stay as they are. Clear description, brand, category or type with null, or replace the full tag list.

Instructions

Change the fields of one product. Send only the fields that change: the fields you leave out stay as they are.

Send null to clear description, brand, productCategory or productType. tags replaces the whole tag list.

Use it for one product. To change the status, brand, category, description or tags of many products, use sirv_bulk_edit_products. To link images, use sirv_link_assets_to_product.

It overwrites the values you send. For a product linked to Shopify, Studio also sends the synced fields to the store in the background when your role may publish to Shopify. Returns the updated product.

Credits: free.

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": {
      "id": "<id>"
    },
    "name": "sirv_update_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesProduct id, from sirv_list_products
skuNoNew SKU, up to 100 characters
nameNoNew name, up to 255 characters
tagsNoThe complete tag list, up to 50 tags. Replaces the old tags; [] removes them all
brandNoBrand name. null clears it
orgIdNoWorkspace id from sirv_list_organizations. Default: the workspace you signed in to
statusNoNew status
descriptionNoNew description, up to 5000 characters. null clears it
productTypeNoProduct type. null clears it
productCategoryNoCategory name. null clears it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.1.1
    • changedInput schema / properties / brand / description
      Previous value: -"Brand (null to clear)"New value: +"Brand name. null clears it"
    • changedInput schema / properties / description / description
      Previous value: -"New description (null to clear)"New value: +"New description, up to 5000 characters. null clears it"
    • changedInput schema / properties / id / description
      Previous value: -"Product ID"New value: +"Product id, from sirv_list_products"
    • changedInput schema / properties / name / description
      Previous value: -"New name"New value: +"New name, up to 255 characters"
    • changedInput schema / properties / orgId / description
      Previous value: -"Organization ID (uses default org if omitted)"New value: +"Workspace id from sirv_list_organizations. Default: the workspace you signed in to"
    • addedInput schema / properties / orgId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • changedInput schema / properties / productCategory / description
      Previous value: -"Category (null to clear)"New value: +"Category name. null clears it"
    • changedInput schema / properties / productType / description
      Previous value: -"Product type (null to clear)"New value: +"Product type. null clears it"
    • changedInput schema / properties / sku / description
      Previous value: -"New SKU"New value: +"New SKU, up to 100 characters"
    • changedInput schema / properties / tags / description
      Previous value: -"Tags array"New value: +"The complete tag list, up to 50 tags. Replaces the old tags; [] removes them all"
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare write/destructive/idempotent/open-world; the description adds the partial-update contract (omitted fields are preserved), null-clearing semantics, that tags replaces the full list, that values are overwritten, and a non-obvious side effect: synced fields are pushed to a linked Shopify store in the background if the role may publish. It also states the return value and 'Credits: free', none of which annotations cover.

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 purpose, then update semantics, clearing rules, routing, side effects, and return value in short scannable sentences. Minor redundancy: 'Use it for one product' restates the opening sentence's scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter mutation with no output schema, the description covers everything an agent needs: which fields are patchable, how to clear values, list-replacement behavior, role-gated Shopify propagation, and that the updated product is returned. Nothing material is left to inference.

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 coverage is 100% and the schema already documents null-clearing per field and the tags replacement, so much of the description is reinforcement. It still adds real meaning at the payload level — 'send only the fields that change, omitted fields stay' — a PATCH contract the schema does not state and that prevents accidental clobbering.

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?

Opens with a specific verb+resource and scope: 'Change the fields of one product.' It immediately distinguishes itself from sirv_bulk_edit_products (many products) and sirv_link_assets_to_product (image linking), so an agent can route correctly without opening sibling schemas.

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

Usage Guidelines5/5

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

Explicit when-to-use ('one product') and when-not, naming two concrete alternatives with the conditions that select them: bulk changes of status/brand/category/description/tags go to sirv_bulk_edit_products, image linking goes to sirv_link_assets_to_product.

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