vivid-ads-commerce

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.

Input Schema

TableJSON 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)

TDQS

A4.6/5.0

Behavior5/5

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

The description goes far beyond the annotations by disclosing key behavioral details: it reuses only previously approved artwork, always re-issues a fresh proof, reprices with current pricing, creates a proof-gated draft, and never charges a card. This adds significant contextual information beyond the structured fields.

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?

The description is a single dense paragraph, but it remains readable and front-loads the main purpose. Each sentence contributes unique information (artwork policy, proof, pricing, draft, no charge). It could be slightly more structured with bullets, but the information-to-word ratio is strong.

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 tool with 9 parameters and no output schema, the description covers all critical aspects: prerequisites, sub-actions, artwork handling, proof workflow, pricing, confirmation behavior, and charging semantics. An agent can correctly select and drive this tool end-to-end based solely on the description.

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?

Although schema description coverage is high (89%), the description adds essential meaning to parameters like action ('list' shows past orders, 'reorder' repeats one), confirm (draft, proof-gated, never charges), and artwork (default reuse previous). This contextual enrichment goes beyond the schema's basic property descriptions.

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 opens with a specific verb + resource: 'Reorder a customer's previous signage job' — this clearly distinguishes it from new-order tools like vivid_place_order. It also clarifies the two sub-actions (list vs reorder), leaving no doubt about the tool's scope.

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?

The description explicitly states the prerequisite of identity verification and contrasts with using just an order number. It implies the need to call vivid_identity_verify first (referenced by the token), and clearly differentiates the list and reorder modes. However, it does not explicitly name sibling tools to prefer over alternatives, which would earn a 5.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation2/5

Several tools have overlapping purposes, particularly order status (vivid_order_status vs vivid_fulfilment_order_status vs vivid_fulfilment_production_stage) and artwork handling (vivid_artwork vs vivid_upload_artwork). An agent could easily select the wrong one without careful reading of the descriptions.

Naming Consistency4/5

All tools share the consistent 'vivid_' prefix and snake_case format. However, the second part mixes verb-noun patterns (place_order, check_artwork) with noun-based names (price, product, order_status), so the pattern isn't fully uniform but is still predictable and readable.

Tool Count3/5

At 25 tools, the server is at the heavy end of the borderline range. The broad scope (product discovery, pricing, ordering, artwork, fulfilment statuses, support) justifies most tools, but some overlapping status/artwork tools could be consolidated to reduce clutter.

Completeness4/5

The server covers the entire customer journey from product search, configuration, pricing, quoting, ordering, artwork upload/check, proof tracking, production/delivery status, to reordering. Minor gaps like explicit order update/cancel tools are missing, but support_answer covers those topics and the lifecycle is otherwise well-covered.

Resources

Need Help?