Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Set product currency prices

set_product_currency_prices
Destructive

Sets a product’s prices in additional currencies and optional per-variant currency prices without changing stock, SKU, or default-currency price; replaces the stored currency price list.

Instructions

Set a product's prices in the workspace's additional currencies (update_cart_config additionalCurrencies), e.g. [{currency: 'EUR', price: 4500, tiers: [{minQty: 10, price: 4000}]}]. Prices and breaks are minor units of each currency; nothing is converted from the default-currency price. price is read only while the product has no variants - a product with variants takes each variant's price from variants (here) and these tiers price every variant without breaks of its own in that currency (price null keeps just the tiers). variants sets each variant's prices per currency by its key (list_products variants[].key), e.g. [{variantKey, prices: [{currency: 'EUR', price: 4500}]}], and never touches stock, SKU or the default-currency price - this is the safe way to price variants per currency; prefer it over set_product_variants currencyPrices, which rewrites every variant's stock and SKU. A product with no price in a sales channel's currency is not sold on that channel (NO_PRICE_IN_CURRENCY). prices replaces the record's whole list: send every currency the product keeps. A variant removed while the call ran fails it with CONFLICT - re-read list_products and retry.

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": {
      "recordId": "<recordId>",
      "prices": "<prices>"
    },
    "name": "set_product_currency_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
pricesYesThe product's whole list of prices in additional currencies; it replaces what is stored, [] clears it. Each currency must be one of the workspace's additional currencies
recordIdYesProduct record id
variantsNoPer-variant prices in additional currencies, written in the same update as prices. Omit to leave every variant's prices untouched; a variant left out keeps its prices; a variant's prices: [] clears them. Never touches a variant's default-currency price, SKU or stock

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnly=false and destructive=true; the description goes far beyond by disclosing that prices replaces the record's whole list, that nothing is converted from the default-currency price, that variants are never touched for stock/SKU/default price, that missing currency pricing causes NO_PRICE_IN_CURRENCY and blocks the sales channel, and that a removed variant fails the call with CONFLICT. These are exactly the mutation risks an agent needs before calling.

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?

Dense but front-loaded: the primary purpose and example come first, then the product-vs-variant distinction, then the replacement and conflict semantics. Some parenthetical asides (e.g. repeated minor-unit notes, 'here', 'price null keeps just the tiers') add nesting that costs readability, but no sentence is filler for a tool this complex.

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 3-parameter destructive write with no output schema, the description covers replacement semantics, unit conventions, variant cascade rules, the no-conversion rule, a downstream sales-channel consequence, and a concurrency/error path. Nothing an agent needs to invoke it safely appears to be missing.

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 still adds relational meaning the schema cannot express — that price is read-only while the product has variants, that product tiers also price every variant lacking its own breaks in that currency, that price null keeps only the tiers, and where variantKey comes from (list_products variants[].key). It mostly restates units (minor units) that the schema already covers, which keeps it short of a 5.

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?

Starts with a specific verb+resource+scope: setting a product's prices in the workspace's additional currencies, tied to update_cart_config additionalCurrencies. It then carves out precise sub-cases (product price vs. per-variant prices) and explicitly distinguishes itself from the sibling set_product_variants currencyPrices, so an agent can route correctly without opening either 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?

Gives explicit when-to-use guidance ('this is the safe way to price variants per currency; prefer it over set_product_variants currencyPrices, which rewrites every variant's stock and SKU') and a clear when-not. It also states the replacement contract ('send every currency the product keeps') and a recovery path (re-read list_products and retry on CONFLICT), leaving little to inference.

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

Deploy Server

Other Tools