vivid-ads-commerce

Show volume price breaks

vivid_price_breaks

Read-onlyIdempotent

Vivid's REAL published volume price breaks for a product + size (e.g. 1 → $135 ea, 2 → $132.30, 5 → $128.25, 10 → $121.50 — save 10%). Use for bulk/trade pricing questions, or right after a price when a slightly larger quantity would save the customer money. Prices are AUD incl. GST and come from the same source as the live price, so they can never contradict a quote. If the product has no breaks it says so — never invent a discount.

Input Schema

Name	Required	Description
`size`	No	size — breaks are per size/variant
`product`	Yes	product name, e.g. 'premium pull up banner'
`quantity`	No	the customer's current quantity, to highlight the next worthwhile break

Output Schema

Name	Required	Description
`size`	No
`tiers`	No	[{ qty, unitPrice }] real published breaks, AUD incl. GST
`status`	Yes	outcome discriminator, e.g. ok / priced / need_size / manual_quote / unknown_product / error
`message`	No
`product`	No
`nextTier`	No
`agent_note`	No
`currentTier`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "agent_note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "currentTier": {},
+    "message": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "nextTier": {},
+    "product": {},
+    "size": {},
+    "status": {
+      "description": "outcome discriminator, e.g. ok / priced / need_size / manual_quote / unknown_product / error",
+      "type": "string"
+    },
+    "tiers": {
+      "description": "[{ qty, unitPrice }] real published breaks, AUD incl. GST"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

AddedJul 19, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already declare a safe read (readOnly, idempotent, non-destructive). The description adds material behavior beyond that: prices are AUD incl. GST, sourced identically to the live price so they can never contradict a quote, and it explicitly discloses the no-breaks case with a guardrail against inventing discounts.

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?

Front-loads purpose and scope, then usage, then source/currency guarantees, then the edge-case guardrail. The inline example prices are illustrative but slightly pad the opening; otherwise every sentence earns its place.

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?

An output schema exists, so return structure need not be explained. The description covers the remaining agent needs — currency, GST, pricing provenance, and the no-breaks fallback — leaving nothing essential for correct invocation missing.

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 the schema already documents product, size (per variant), and quantity. The description reinforces the quantity semantics (highlighting 'the next worthwhile break') and shows the break mapping, but adds only marginal detail over the schema. Baseline 3 applies.

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 (volume price breaks for a product + size) with concrete example values. It explicitly distinguishes itself from the sibling vivid_price by noting the prices 'come from the same source as the live price,' so an agent can tell the two apart without opening schemas.

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?

Gives clear triggering contexts: 'bulk/trade pricing questions, or right after a price when a slightly larger quantity would save the customer money.' This effectively positions it against vivid_price by usage scenario, though it never explicitly names the alternative or states when not to call it.

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

All vivid-ads-commerce 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?