vivid-ads-commerce

Reorder a past job (creates a draft)

vivid_reorder

Reorder a customer's previous signage job — fast. Requires identity verification (emailed one-time code), not just an order number. action:'list' shows their past orders; action:'reorder' repeats one. ARTWORK: it reuses only the customer's previously APPROVED artwork (the print file), never a pre-approval upload; if it can't be confirmed automatically the team confirms it. A fresh proof is ALWAYS re-issued to confirm the artwork before printing. The customer may also supply new artwork or change the quantity. Re-prices with CURRENT pricing (never the old price). Creates a proof-gated draft order; never charges a card. CODE REQUIRED: needs the customer's email AND a verified identity token. Without a token this tool emails the customer a 6-digit code and returns status need_verification with a verificationId — ask the customer for the code, call vivid_identity_verify, then call this tool again with the token. It shows nothing before that.

Input Schema

Name	Required	Description
`name`	No
`email`	Yes	the email the customer ordered under (required to find past orders)
`order`	No	order name to reorder from, e.g. '#D12345' (optional)
`token`	No	the identity token from vivid_identity_verify (required — proves the customer owns this email)
`action`	No	'list' (show past orders) or 'reorder' (repeat one)
`artwork`	No	new print-ready artwork file URL (optional; default = reuse previous)
`confirm`	No	set true to place the reorder (draft, proof-gated, never charges)
`product`	No	which product to reorder, e.g. 'corflute' (optional; default = most recent eligible)
`quantity`	No	override quantity (optional; default = same as last time)
`idempotency_key`	No	optional: a unique key for this request — a retry with the same key returns the first result instead of repeating the action

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

addedInput schema / properties / idempotency_key

Added value: +{
+  "description": "optional: a unique key for this request — a retry with the same key returns the first result instead of repeating the action",
+  "maxLength": 128,
+  "type": "string"
+}

First observedJul 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only give generic safety hints (readOnlyHint=false, destructiveHint=false, openWorldHint=true). The description adds critical behavior far beyond those: verified identity required, only APPROVED artwork is reused, a fresh proof is ALWAYS re-issued, re-pricing uses CURRENT pricing, it never charges a card, and the exact need_verification/verificationId return flow. This is exactly the behavioral detail a mutating tool needs.

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?

It is long but front-loaded: purpose and verification requirement come first, then artwork rules, then pricing, then the code-required flow. Nearly every sentence carries operational weight (artwork constraints, pricing, no-charge). Slightly dense with caps emphasis, but not padded.

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 10-parameter, multi-step, proof-gated tool with no output schema, the description covers the full lifecycle: prerequisite verification, the two actions, artwork validation, re-pricing, draft creation, and the exact fallback return (need_verification + verificationId). An agent has everything needed to call it and handle the response.

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 already 90%, so the baseline is 3. The description adds meaning beyond the schema by explaining the token prerequisite flow, the artwork-reuse default vs. supplying new artwork, quantity override, and the confirm-to-place semantics, tying parameters to the overall verification workflow.

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?

The description states a specific verb and resource ('Reorder a customer's previous signage job') and clarifies the output ('creates a proof-gated draft order'), which distinguishes it from vivid_place_order and vivid_accept_quote. An agent can immediately tell what the tool does and what it produces.

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?

Explicitly defines the two modes ('action:list' vs 'action:reorder'), states the prerequisite (identity verification via emailed one-time code), and names the alternative tool to route through (vivid_identity_verify). The 'when-not' is also implicit but clear: it shows nothing before verification.

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?