vivid-ads-commerce

vivid_upload_artwork

Upload a customer's artwork FILE through the agent (no website file picker needed). Accepts the file as base64, stores it in Vivid's Google Drive, and returns a stable shareable link plus metadata. Accepts PDF / AI / EPS / JPG / PNG. Does NOT verify print-readiness — the team checks that. Uploading needs no verification, but ATTACHING the file to an existing order does: pass the identity token from vivid_identity_verify, otherwise the file is held unattached and the reply says so. Use when a customer wants to send their print file via chat.

Input Schema

TableJSON Schema

Name	Required	Description
`email`	No	customer email (optional). Only recorded once verified — see token.
`token`	No	identity token from vivid_identity_verify. Required to attach this upload to an order or to record the email; without it the file is still stored, just not claimed by anyone.
`orderId`	No	attach to an existing order (optional). Ignored unless a valid token is supplied — an unverified caller must not be able to put a file on somebody else's order.
`quoteId`	No	associate with a quote request (optional)
`filename`	Yes	original filename incl. extension, e.g. 'banner-artwork.pdf'
`mimeType`	No	MIME type, e.g. 'application/pdf'
`sessionId`	No	associate with a design session (optional)
`contentBase64`	Yes	the file contents, base64-encoded (data URI prefix OK). Small files only; for very large files share a download link instead.

TDQS

A4.6/5.0

Behavior5/5

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

The description goes well beyond annotations by disclosing that the file is stored in Google Drive, that print-readiness is not verified, and that without an identity token the file is held unattached with the reply 'says so'. This provides crucial behavioral context that annotations (readOnlyHint, destructiveHint, etc.) do not cover.

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 a compact four-sentence paragraph that front-loads the main purpose and includes only essential details. Every sentence contributes meaning: the action, the input/storage/return, the format and print-readiness caveat, the verification flow, and a clear usage trigger. No unnecessary wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema, the description adequately explains the return value (shareable link plus metadata) and covers the critical token-attachment flow and file format constraints. It does not detail specific failure modes beyond unattached files, but the schema covers most parameter-level edge cases, making the description sufficiently complete for an 8-parameter tool.

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. The description adds value by explicitly listing accepted file formats (PDF/AI/EPS/JPG/PNG) and reinforcing the token's role in attachment, which complements the detailed schema descriptions. This provides some extra semantic meaning beyond the schema.

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 primary action: 'Upload a customer's artwork FILE through the agent', specifies the input mechanism (base64), the storage location (Google Drive), and the return value (shareable link plus metadata). This distinguishes it from sibling tools like vivid_artwork or vivid_check_artwork, which focus on different aspects of artwork handling.

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 gives explicit usage context: 'Use when a customer wants to send their print file via chat.' It also explains the token requirement for attaching to an order, clarifying when verification is needed. However, it does not explicitly mention when not to use this tool or name alternative tools.

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?