vivid-ads-commerce

Check digital-proof status

vivid_proof_status

Read-onlyIdempotent

Check a customer's DIGITAL PROOF status: has the proof been emailed, is it awaiting their approval, being revised after rejection, or already approved (production underway). Use for 'where's my proof', 'did you send my proof', 'when do I approve'. Requires the order number AND the email on the order (identity — details only return when they match). Relay the returned agent_hint concisely; production starts only after the customer approves the emailed proof. 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`	Yes	the email address the order was placed under (required)
`token`	No	identity token from vivid_identity_verify. Without it the proof STATE is returned but not the approve/reject link.
`order_number`	Yes	order number, e.g. '#121978'

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

addedInput schema / properties / token

Added value: +{
+  "description": "identity token from vivid_identity_verify. Without it the proof STATE is returned but not the approve/reject link.",
+  "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 already say readOnly/idempotent/non-destructive, but the description adds substantial behavioral context beyond them: identity must match or nothing returns, an emailed 6-digit code triggers need_verification with a verificationId, the agent must call vivid_identity_verify and retry with the token, and production only begins after customer approval. This is exactly the kind of workflow disclosure annotations cannot carry.

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-loaded with the state enumeration and caller phrasings before the mechanics. Slightly redundant — 'Requires the order number AND the email' is restated as 'CODE REQUIRED: needs the customer's email' — but every sentence carries actionable information, so the length is earned.

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?

No output schema exists, yet the description names the returned artifacts an agent must act on (agent_hint, need_verification, verificationId) and the production-start condition. Combined with the fully documented input schema, nothing needed to invoke or follow up is missing.

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 baseline is 3, but the description adds real meaning: it explains that email is used for identity matching (not just a lookup key) and that token gates whether the approve/reject link is returned. It also clarifies the two-required-parameter contract via the 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?

States a specific verb and resource ('Check a customer's DIGITAL PROOF status') and enumerates the possible states (emailed, awaiting approval, being revised, approved/production underway). An agent can distinguish it from vivid_order_status or vivid_fulfilment_production_stage without opening any schema.

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?

Gives concrete caller phrasings ('where's my proof', 'did you send my proof') that map directly to the tool, states the prerequisites (order number AND matching email), and routes to the sibling vivid_identity_verify inside a step-by-step flow. When-to-use is explicit rather than inferred.

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?