Skip to main content
Glama

save_store_product

Destructive

Create or edit a store product. Use revision 0 to create, or the current revision to edit. Money amounts are in minor units of the store currency.

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": {
      "id": "<id>",
      "name": "<name>",
      "sku": "<sku>",
      "price": "<price>",
      "currency": "<currency>",
      "revision": "<revision>"
    },
    "name": "save_store_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
skuYes
nameYes
priceYes
activeNo
currencyYes
revisionYes
descriptionNo
requiresShippingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=false, so the safety profile is largely covered. The description adds valuable optimistic-concurrency semantics via revision and the minor-units convention, but does not say that omitted optional fields (active, description, requiresShipping) fall back to defaults rather than being preserved, which matters for an overwriting save.

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?

Three short sentences with zero padding; the capability statement comes first, then the create-vs-edit rule, then the money-unit convention. Nothing here is redundant with the annotations or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter, 6-required, destructive save with no output schema and no field-level schema docs, the description covers mode selection and amount encoding but not failure behavior on stale revisions, whether id is caller-generated, or how unspecified optional fields are treated. Adequate to call correctly in the happy path, incomplete for the edge cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 9 parameters, so the description must carry the load. It explains the two hardest ones well — revision semantics and that price/currency are in minor units — but leaves id (client-supplied UUID), sku, name, active, description and requiresShipping entirely unannotated for meaning beyond their types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb pair and resource ("Create or edit a store product"), which is precise enough that an agent knows this is the write path for catalogue products. It does not explicitly contrast with the nearby save_booking_product sibling, but the resource noun (store product) is distinct enough to disambiguate in practice.

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?

It gives an actionable routing rule for the two modes: revision 0 to create, current revision to edit. That is real when-to-use guidance rather than implied usage. It stops short of saying when not to use this tool (e.g., for stock levels use adjust_store_stock) or what to do on a revision conflict.

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