Skip to main content
Glama

Bulk Edit Products

sirv_bulk_edit_products
Destructive

Apply one change—status, fields, or linked assets—to multiple products in a single call, or delete up to 25 products; use for bulk edits instead of individual product updates.

Instructions

Make one change to many products in one call. action picks the change:

  • updateStatus: set status on every product in productIds.

  • updateFields: set fields (brand, productCategory, description, status, tags) on every product. With tagMode merge the tags are added; with replace they take the place of the old tags.

  • linkAssets: link assetIds to every product, with an optional role. A main role takes one asset.

  • delete: delete up to 25 products. Products have no trash, so this cannot be undone: ask the user first.

Use it for several products. For one product, use sirv_update_product or sirv_delete_product.

For products linked to Shopify, Studio also sends status and field changes to the store in the background when your role may publish to Shopify. Products that you may not change are skipped and listed in denied. Returns how many products changed.

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": {
      "action": "<action>"
    },
    "name": "sirv_bulk_edit_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoFor linkAssets: the images' role. main takes one asset
orgIdNoWorkspace id from sirv_list_organizations. Default: the workspace you signed in to
actionYesThe change to make to every product
fieldsNoNeeded for updateFields: the fields to set on every product. Fields you leave out stay
statusNoNew status. Needed for updateStatus
tagModeNoFor updateFields with tags: merge adds the tags, replace swaps the old tags for these. Default: mergemerge
assetIdsNoIds of the library assets to link, up to 100. Needed for linkAssets
productIdsNoIds of the products to change, from sirv_list_products. At most 25 for delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=false and openWorld=true, but the description goes further: 'delete' has no trash and cannot be undone (with an instruction to ask the user first), products the caller cannot change are skipped and listed in `denied`, and Shopify-linked products trigger background status/field propagation when the role may publish. That is meaningful context beyond the structured hints, though it does not quantify scope limits beyond the 25-product delete cap.

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?

Front-loaded with the core purpose, then a bulleted action breakdown, then sibling routing, then side effects and return value. Every sentence carries distinct information; even the short 'Credits: free.' line adds cost context.

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?

No output schema exists, yet the description explicitly covers the return ('Returns how many products changed') and the `denied` list. For an 8-parameter, four-action, destructive bulk mutation with Shopify side effects, all the information needed to call it correctly is present.

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%, so the baseline is 3, but the description adds cross-parameter semantics the schema cannot express: which parameter applies to which `action`, how `tagMode` merge vs replace behaves on tags, and that a `main` role accepts only one asset. Remaining gap is minor edge behavior (e.g. what happens when assetIds exceed 100) which is technically in the schema.

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 ('Make one change to many products in one call') and immediately enumerates the four supported operations (updateStatus, updateFields, linkAssets, delete) with their targets. It also names the single-product siblings it is not, so an agent can distinguish it without opening any schema.

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 routing rule: 'Use it for several products. For one product, use sirv_update_product or sirv_delete_product.' Each action bullet also states when it applies and which parameter drives it, leaving nothing to inference.

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