stub

Save product

save_product

Create or update the catalogue PRODUCT itself (name, price, account); for a size, colour or other option of an existing product, use save_variant. Pass an id to update that product; omit id to create a new one. Returns the new product id on create. To create/update many at once, send an items array — one all-or-nothing transaction with a single ledger recompute; each item with an id updates, each without creates.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	Product id. Present → update that product; omit → create a new one.
`sku`	No	Stock-keeping unit / product stock code. Canonical product-level SKU (mirrors a variant's sku).
`cost`	No	Cost price per unit.
`name`	No	Display name / description of the product.
`unit`	No	Legacy unit-of-measure label; prefer `units`.
`image`	No	Product image URL; pass "$delete" to remove the existing image.
`items`	No	Vector of product objects to create/update in one all-or-nothing batch. Preferred over repeated calls. Each item with an id updates; each without creates.
`notes`	No	Free-text notes.
`price`	No	Selling price per unit, in the record's currency.
`units`	No	Unit of measure label (e.g. "each", "hour", "kg").
`amount`	No	Unit amount before quantity/tax, in the record's currency.
`starred`	No	Whether the product is starred/favourited.
`currency`	No	ISO 4217 currency code (e.g. "ZAR", "USD"). Defaults to the business currency.
`quantity`	No	Number of units.
`trackstock`	No	Whether stock levels are tracked for this product.
`description`	No	Product description.
`paymentlink`	No	Whether an online payment link is enabled for this product.
`salestaxids`	No	Sales tax ids to link to this product.
`unlinktaxes`	No	Sales tax ids to unlink from this product.
`costcurrency`	No	ISO 4217 currency code for the cost price.
`allowoversell`	No	Whether the product can be sold beyond available stock.
`enablequantity`	No	Whether the buyer can choose a quantity for this product.
`requireaddress`	No	Whether a delivery/billing address is required when this product is purchased.
`salestaxexclusive`	No	Whether the price excludes sales tax.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 11, 2026

addedInput schema / properties / items / items / properties / sku

Added value: +{
+  "description": "Stock-keeping unit / product stock code. Canonical product-level SKU (mirrors a variant's sku).",
+  "type": "string"
+}

addedInput schema / properties / sku

Added value: +{
+  "description": "Stock-keeping unit / product stock code. Canonical product-level SKU (mirrors a variant's sku).",
+  "type": "string"
+}

First observedSep 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description carries most of the behavioral load and it does: it discloses the create-vs-update switch on `id`, the returned product id on create, and that batch `items` are one all-or-nothing transaction with a single ledger recompute. It does not mention permission/auth requirements or what a partial-failure response looks like, which keeps it short of a 5.

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 dense sentences that are front-loaded with the primary purpose, then the sibling exclusion, then the id/batch mechanics. No filler; each clause maps to a decision the agent must make.

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

Completeness4/5

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

For a 24-parameter, no-required-fields tool with no output schema, the description covers create/update semantics, batch semantics, and the create return value. It omits anything about defaults (e.g. currency defaulting to business currency) and error/rollback behavior beyond 'all-or-nothing', leaving a small gap.

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 100%, so every parameter is already documented; the description's id and items semantics largely restate what the schema says. Baseline 3 applies, with only marginal added meaning (e.g. batch being preferred over repeated calls).

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 specific verb and resource ('Create or update the catalogue PRODUCT itself') plus the field scope, and explicitly distinguishes itself from the save_variant sibling for size/colour options. An agent can route between save_product and save_variant 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 routing rules: use save_variant for options of an existing product, pass an `id` to update, omit `id` to create, and use the `items` array for batch work instead of repeated calls. Both the alternative tool and the create/update condition are named.

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

All stub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?