vivid-ads-commerce

Check order status

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. 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
`email`	No	the email the order was placed under (always required)
`token`	No	identity token from vivid_identity_verify (required to see any details; without it a code is emailed to the customer)
`reference`	No	order # or quote/draft # (e.g. '#119581' or '#D776755')

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 20, 2026

changedInput schema / properties / email / description

Previous value: -"alternatively, the customer's email to list recent orders (requires verified identity)"New value: +"the email the order was placed under (always required)"

addedInput schema / properties / token

Added value: +{
+  "description": "identity token from vivid_identity_verify (required to see any details; without it a code is emailed to the customer)",
+  "type": "string"
+}

First observedJul 19, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations, the description discloses critical behavior: live data sources (Enfocus Switch, StarShipit), finality rules for shipped/delivered orders, the requirement for customer email and a verified identity token, and the fallback flow where a 6-digit code is emailed and need_verification is returned. It also states that no details are shown before verification, which is important operational context.

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 front-loaded and most sentences serve the auth/status context. There is slight redundancy around the email requirement appearing twice, but the overall length is justified by the complex verification workflow.

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?

With no output schema and no required parameters declared, the description compensates well by explaining the possible status categories, the verification fallback response, and the required follow-up call to vivid_identity_verify. An agent has enough information to invoke the tool and handle the common unauthenticated path.

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 100%, so the schema already documents each parameter. The description still adds meaning beyond the schema by stating that the email must match the order, that the token comes from vivid_identity_verify, and that without a token the tool emails a code and returns need_verification.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource: checking LIVE order status, including production stage, pickup readiness, or shipping details from named systems. It is clear what the tool does, but it does not explicitly distinguish itself from sibling fulfilment-status tools such as vivid_fulfilment_order_status or vivid_fulfilment_shipping.

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?

It gives concrete use cases ('where is my order', 'track order 12345', 'is my order ready') and describes the identity-verification workflow with vivid_identity_verify. However, it does not state when not to use this tool or compare it against sibling alternatives.

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?