Skip to main content
Glama

MyProduct: Update Price or Stock

update_managed_store_product
Destructive

[Store Products] [What it does] Changes selling price, cost, compare-at price, currency, or stock for exact variants of one DSers-managed store product, and handles the matching auto-sync switches. [When to use] Use it when the user asks to change an existing product's price, cost, or stock, and when the agent has already resolved the exact variants and target values. Trigger words: change the store price, reprice a live product, update stock, update cost. [When not to use] To inspect current prices, stock, or variants, use get_managed_store_product. For a product not yet pushed to a store — an item still on the DSers Import List — use update_pre_publish_product_price. To change or apply a store Pricing Rule in bulk, use the pricing-rule or bulk-price Tool. It edits one product only and cannot bulk-reprice by filter. [How to use]

  • Resolve IDs in order: dsers_store_id from list_stores, dsers_product_id from list_managed_store_products items[].dsers_product_id, and sales_product_variant_id from get_managed_store_product sales_product_variant_list[].sales_product_variant_id. SKUs, option text, and supplier variant IDs are rejected.

  • Every price_updates item requires sales_product_variant_price_amount, so resend the current selling price even when only sales_product_variant_cost_amount, sales_product_variant_compare_at_price_amount, or currency changes.

  • Amounts are major-unit decimal strings ("19.99", never "1999"), and currency sets the allowed precision; omit it only when the variant or product already has one.

  • sales_product_variant_inventory_quantity replaces the current quantity and is never a delta.

  • price_auto_sync_action is mandatory with price updates and stock_auto_sync_action with stock updates; disable permanently turns that sync off.

  • This write is not idempotent. Send it once, for at most 100 variants of a single product.

  • Compare price_variants_updated and stock_variants_updated with what you requested; if they differ or the outcome is unknown, re-read with get_managed_store_product instead of retrying. Subscription errors block the write and are returned as structured errors.

  • This tool covers only products already pushed to a store, including Draft status; for items not published yet, use update_pre_publish_product_price. If the publish state is unclear, or the product exists on both sides, ask before changing the live price. [Side effects] Changes buyer-visible prices and stock; disable also switches off auto-sync. [Confirmation] Required: show store, product, variants, and final values first.

Input Schema

NameRequiredDescriptionDefault
price_updatesNoPaste a JSON array into this field. Example: [{"sales_product_variant_id":"45382179012608","sales_product_variant_price_amount":"19.99","currency":"USD"}]. Copy sales_product_variant_id from get_managed_store_product. Price, cost, and compare-at values use human-readable major currency units. Optional fields: sales_product_variant_cost_amount, sales_product_variant_compare_at_price_amount, currency — omit cost or compare-at price to preserve its current minor-unit value; omit currency only when the resolved variant or product already has one. Use one object per variant and include price_auto_sync_action whenever price_updates is present. Paste JSON example: [{"currency":"USD","sales_product_variant_id":"45382179012608","sales_product_variant_price_amount":"19.99"}].
stock_updatesNoPaste a JSON array into this field. Example: [{"sales_product_variant_id":"45382179012608","sales_product_variant_inventory_quantity":100}]. Copy sales_product_variant_id from get_managed_store_product response sales_product_variant_list[].sales_product_variant_id. Inventory quantity must be non-negative and replaces the current value. Use one object per variant and include stock_auto_sync_action whenever stock_updates is present. Paste JSON example: [{"sales_product_variant_id":"45382179012608","sales_product_variant_inventory_quantity":100}].
dsers_store_idYesCopy from list_stores response dsers_store_id field. Decimal string like "123456". Do not use store names, domains, or guessed numbers. Required.
dsers_product_idYesCopy from list_managed_store_products response items[].dsers_product_id field. This is the DSers-managed product ID, not a sales-platform product ID or supplier product ID. Required.
price_auto_sync_actionNoRequired whenever price_updates is present. Use disable for requests such as turn off/close/stop price synchronization or 价格自动同步关掉. Use keep for requests such as keep/preserve/leave price synchronization unchanged or 价格同步保持. If the user already stated a preference, map it directly and do not ask again.
stock_auto_sync_actionNoRequired whenever stock_updates is present. Use disable for requests such as turn off/close/stop inventory synchronization or 库存自动同步关掉. Use keep for requests such as keep/preserve/leave inventory synchronization unchanged or 库存同步保持. If the user already stated a preference, map it directly and do not ask again.

Output Schema

NameRequiredDescriptionDefault
auto_sync_resultsYesRequested automatic-sync actions, prior states, actions taken, and resulting states
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.
price_variants_updatedYesNumber of price variant writes acknowledged
stock_variants_updatedYesNumber of stock variant writes acknowledged

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/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: it warns that the write is non-idempotent and should be sent once, that 'disable' permanently turns off auto-sync, that changes are buyer-visible, that subscription errors block the write, and that the agent should re-read rather than retry when counts differ. It also mandates confirmation with the final values shown. No contradiction with the supplied hints.

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?

The bracketed section headers ([What it does], [When not to use], [How to use], [Side effects], [Confirmation]) front-load the critical routing and safety information effectively. It is long, and update_pre_publish_product_price is cited in two separate sections, which is a minor redundancy for an otherwise tightly organized definition.

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 destructive, non-idempotent write with 6 parameters and an output schema, the description covers everything an agent needs: preconditions, ID sourcing, format rules, sync-switch semantics, side effects, and how to verify outcome via the returned counts. Return-value detail is appropriately deferred to the output schema.

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; the description exceeds it by explaining cross-field behavior the schema cannot state on its own: ID resolution order via list_stores, list_managed_store_products, and get_managed_store_product; that a price amount must be resent whenever cost, compare-at, or currency changes; that quantities are absolute, not deltas; and that auto-sync actions are mandatory alongside their corresponding arrays. These are genuine additions, though some overlap with the already-detailed field descriptions.

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 states a precise verb and resource ('Changes selling price, cost, compare-at price, currency, or stock for exact variants of one DSers-managed store product') and explicitly separates itself from get_managed_store_product, update_pre_publish_product_price, and the bulk pricing tools. An agent can identify the tool's scope without opening the 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?

It gives explicit when-to-use conditions, trigger phrases, and a when-not-to-use block naming concrete alternative tools. It also handles the ambiguous case (product exists on both sides, publish state unclear) by instructing the agent to ask rather than guess, so nothing is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.