vivid-ads-commerce

Get a quote's payment link

vivid_accept_quote

Read-onlyIdempotent

Return the secure payment link for a formal quote Vivid already emailed (e.g. #D786069) so the customer can complete the order without leaving the conversation. Requires the quote number AND the email it was sent to (identity). Read-only — nothing is charged; it returns the customer's existing Shopify checkout link. If the quote has already become an order, it says so instead of issuing another link. 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 the quote was sent to (required)
`token`	No	identity token from vivid_identity_verify (required to see any details; without it a code is emailed to the customer)
`quote_number`	Yes	quote/draft number, e.g. '#D786069'

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

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"
+}

AddedJul 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations: nothing is charged, it returns the customer's existing Shopify checkout link, the already-converted-to-order case, and a detailed auth flow (6-digit code emailed, need_verification status, verificationId, 'shows nothing before that'). This is exactly the extra context the readOnly/idempotent hints cannot convey.

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 core purpose before the verification procedure, and each sentence carries operational weight. It is dense and slightly long, but the length is justified by the non-obvious 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, the description still covers return values (payment link, need_verification + verificationId, or order-already-exists) and the full prerequisite chain. An agent has everything needed to invoke it 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 coverage is 100% so the baseline is 3, but the description adds real meaning: quote_number AND email together act as identity, and token must come from vivid_identity_verify, with the consequence of omitting it. It stops short of format details for quote_number beyond the example.

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 ('Return the secure payment link for a formal quote') and scopes it to quotes Vivid already emailed, with a concrete example. An agent can distinguish it from sibling order/quote tools without opening the 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?

Explains when it applies (an emailed formal quote) and when not (if the quote became an order, it says so instead of issuing a link). It names the alternative tool (vivid_identity_verify) and the exact sequence to follow when a token is missing.

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?