vivid-ads-commerce

vivid_order_status

Read-onlyIdempotent

Check the LIVE status of an order — real production stage (from the Enfocus Switch print workflow), ready-for-pickup, or shipped with carrier + tracking (from StarShipit, authoritative). Look up a real order by number (e.g. #119581) or a quote/draft by number (e.g. #D776755). Requires the customer's email, which must match the order. Use for 'where is my order', 'track order 12345', 'is my order ready'. Shipped/delivered from StarShipit is final; otherwise the live Switch stage is returned.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`email`	No	alternatively, the customer's email to list recent orders (requires verified identity)
`reference`	No	order # or quote/draft # (e.g. '#119581' or '#D776755')

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds valuable behavior: requires customer's email matching the order, StarShipit is the authoritative/final source for shipped/delivered, and otherwise the live Switch stage is returned. This goes beyond annotations and sets correct expectations.

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?

The description is packed into five dense sentences, each providing unique value: purpose, data sources, input examples, usage cues, and return semantics. No filler or repetition.

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?

Despite no output schema, the description explains what will be returned (StarShipit final vs. Switch stage), the input requirements (order/quote number, email match), and the authoritative hierarchy. This is sufficient for an agent to know what to expect and how to use the tool correctly.

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 covers both parameters fully, so baseline is 3. The description adds examples for reference format (#119581 vs #D776755), distinguishes order vs quote/draft, and states the email matching requirement. However, there is slight ambiguity: description says 'requires email' while schema lists no required parameters.

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 clearly states the tool's function: 'Check the LIVE status of an order' with specific data sources (Enfocus Switch, StarShipit) and status categories (production stage, ready-for-pickup, shipped). It distinguishes itself from sibling tools by aggregating multiple status sources into one comprehensive status check.

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?

Provides explicit use cases: 'Use for "where is my order", "track order 12345", "is my order ready"'. This gives clear context for when to use the tool, though it does not explicitly mention alternatives or when not to use it (e.g., raw production stage vs. this aggregate).

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?