Skip to main content
Glama

Set product wholesale prices

set_product_price_tiers
DestructiveIdempotent

Replace ONE product's wholesale quantity breaks in ONE currency — 'from 12 units, 12.40 each'. The list you send becomes the whole set for that currency (at most 10; each quantity at least 2 and once; a bigger quantity must cost less per unit); an empty list removes all its breaks. The product must already be priced in that currency. Breaks apply to buyers outside the team (the customer portal and connected partners), never to the website or marketplaces, and the buyer gets the better of a break or their own discount. Idempotent. Returns { count }. Read get_product_pricing first. Echoes the workspace.

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": {
      "currency": "<currency>",
      "id": "<id>",
      "tiers": "<tiers>"
    },
    "name": "set_product_price_tiers"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe product id returned by search_products or get_product — never a SKU or a name.
tiersYesThe wholesale breaks for that currency, at most 10. This list REPLACES the product's breaks in that currency; an empty list removes them all. Each quantity once, and a bigger quantity always costs less per unit.
currencyYesThe currency of these breaks (uppercase 3-letter ISO code). The product must already be priced in it — its own currency or a price-list row.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations (which already flag destructive/idempotent) by disclosing the replace-all semantics, that an empty list deletes every break, the ordering/validation rules, the currency precondition, the discount-interaction behavior, and the return payload ('{ count }'). The workspace echo is also noted, which matters for a mutation whose effect is scoped.

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, with the replacement semantics and the example leading. Every clause carries constraint or scope information; the only mild cost is that several rules echo the schema, making it slightly longer than strictly necessary.

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, so the 'Returns { count }' note and the workspace echo are essential and supplied. Prerequisites, destructive semantics, idempotency, scope limits, and validation rules are all covered for a 3-parameter mutation tool.

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 baseline is 3, but the description adds real business meaning on top of the field docs: the list REPLACES rather than appends, and the product must already be priced in the given currency. It reinforces constraints already in the schema rather than adding new syntax, hence not 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?

States a precise verb+resource+scope: replacing wholesale quantity breaks for exactly one product in one currency, with an inline example ('from 12 units, 12.40 each'). This is distinguishable from the sibling pricing tools (set_product_channel_price, upsert_product_prices, apply_bulk_price_change) which target different pricing surfaces.

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

Usage Guidelines4/5

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

Explicitly names a prerequisite ('Read get_product_pricing first') and delimits who the breaks apply to (outside buyers via the customer portal and connected partners, never the website or marketplaces). It stops short of explicitly contrasting itself against siblings like set_product_channel_price, so it loses the top mark.

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.

Resources