Skip to main content
Glama

products_bulk_action

Destructive

Apply batch operations like price changes or field updates to multiple products in a single request using predefined actions, supporting targeted product IDs or all products.

Instructions

Apply the same actions to many products in one request (PUT /admin/api/ecommerce/v1/products). This is NOT per-row arbitrary updates — every product in target_ids receives every action in actions. For one-off varied edits use product_update.

Request shape:

  • actions: list of {target_field, action, value, source_field?}. Allowed action verbs: set, increase_by_fixed, decrease_by_fixed, increase_by_percent, decrease_by_percent, round, round_upwards, round_downwards, merge, remove.

  • target_ids: list of integer product ids, OR the literal string 'all' to apply to every product on the site.

Response: {counters: {processed, failed}, processed_ids, failed_ids}. Duplicate ids in target_ids are collapsed server-side. No empirical batch-size cap observed up to 1001 ids (Stella, 2026-05-27); send what you need.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYes
actionsYesEach {target_field, action, value, source_field?}. Same actions apply to every id in target_ids.
target_idsYesList of product ids (up to 10000), or the literal string 'all' to target every product on the site. NOTE: target_ids='all' is high blast radius and requires force=true.
forceNoRequired when target_ids='all'. Ignored when target_ids is a list of explicit ids — the caller has already named the rows.
Behavior5/5

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

Annotations indicate destructiveHint=true. Description adds context on request shape, response counters, duplicate id collapsing, and observed batch size limit. No contradiction with annotations.

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?

The description is concise and well-structured: purpose first, then request shape, then response. Every sentence adds value with no redundancy.

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?

Given the complexity (bulk mutation, multiple actions) and no output schema, the description covers purpose, usage, parameters, response structure, edge cases (duplicates, batch size), and force flag behavior.

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 already has descriptions for 3 of 4 parameters (75% coverage). Description adds value by listing allowed action verbs, explaining the 'all' behavior, and noting force is ignored for explicit ids. However, the schema also covers these points adequately.

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 clearly states the tool applies the same actions to many products in one request, and distinguishes it from product_update for one-off varied edits. The verb and resource are specific.

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?

Explicitly says when to use (bulk actions) and when not to (use product_update for varied edits). Also explains the 'all' string and force flag requirement.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/runnel/voog-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server