au.com.vividads/vivid-ads-commerce
REMOTE · AGENT.VIVIDADS.COM.AU · SCANNED AUG 3
Live signage pricing, formal quotes and draft orders from Vivid Ads Australia. Open pre-sales MCP.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5828 tokens (~233/item across 25 items; 25 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · agent.vividads.com.au
claude mcp add --transport http au-com-vividads-vivid-ads-commerce https://agent.vividads.com.au/api/ucp/public/mcp
[mcp_servers.au-com-vividads-vivid-ads-commerce] url = "https://agent.vividads.com.au/api/ucp/public/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"au-com-vividads-vivid-ads-commerce": {
"type": "remote",
"url": "https://agent.vividads.com.au/api/ucp/public/mcp",
"enabled": true
}
}
} openclaw mcp add au-com-vividads-vivid-ads-commerce --url https://agent.vividads.com.au/api/ucp/public/mcp --transport streamable-http
mcp_servers:
au-com-vividads-vivid-ads-commerce:
url: "https://agent.vividads.com.au/api/ucp/public/mcp" {
"mcpServers": {
"au-com-vividads-vivid-ads-commerce": {
"type": "http",
"url": "https://agent.vividads.com.au/api/ucp/public/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://agent.vividads.com.au/api/ucp/public/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agent.vividads.com.au | CN=YE1,O=Let's Encrypt,C=US | 11 Jul 2026 | 9 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5e2192d6d29109891c091917d4a42f84bed |
| SANs: agent.vividads.com.au | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC secure
Validation of agent.vividads.com.au. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| au. | present | 26642, 32902 | 8, 8 | Verified |
| com.au. | present | 14185 | 8 | Verified |
| vividads.com.au. | present | 46561 | 8 | Verified |
| agent.vividads.com.au. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agent.vividads.com.au/api/ucp/public/mcp | Verified | 200 | |
| http (plaintext) | http://agent.vividads.com.au/api/ucp/public/mcp | HTTPS enforced | 301 | https://agent.vividads.com.au/api/ucp/public/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
vivid_accept_quote ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | the email the quote was sent to (required) | |
| quote_number | string | yes | quote/draft number, e.g. '#D786069' |
No output schema declared.
No examples provided.
vivid_artwork ~255
Attach a customer-provided artwork file or link to a signage order (a successful attach does NOT mean it is print-ready — the team still checks it). EASIEST: pass a shareable link to the file (sourceUrl) — Google Drive, Dropbox, WeTransfer, etc. — and use the returned fileUrl in vivid_place_order's artwork {mode:'upload_file', fileUrl}. For a large file with no link yet, set requestUpload:true to get a direct-upload URL (the file uploads straight to storage — handles 50–200MB+), then call again with the returned fileId to get the share link.
| Name | Type | Req | Description |
|---|---|---|---|
| contentType | string | — | — |
| fileId | string | — | after a direct upload completes, pass the returned file id here to finalise and get the share link |
| filename | string | — | filename (required with requestUpload), e.g. 'flyer.pdf' |
| requestUpload | boolean | — | set true to get a direct-upload URL for a large file (client uploads straight to storage) |
| sourceUrl | string | — | a shareable https link to the print-ready artwork (PDF/PNG/JPG/AI/EPS) — the easiest path |
No output schema declared.
No examples provided.
vivid_check_artwork ~168
Check whether a customer's artwork PDF is print-ready BEFORE they order — powered by Vivid's own production preflight engine. Reports size vs the ordered size, bleed, RGB-vs-CMYK colour, font embedding and effective resolution, each with a plain-English fix. ADVISORY ONLY: it never blocks anything. If the customer is happy to proceed with the file as-is, that is always accepted — say so explicitly. Every order also gets a free digital proof before printing.
| Name | Type | Req | Description |
|---|---|---|---|
| file_url | string | yes | downloadable URL of the artwork PDF (e.g. the fileUrl from vivid_upload_artwork) |
| height_mm | number | — | ordered height in mm, if known |
| width_mm | number | — | ordered width in mm, if known — enables the size check |
No output schema declared.
No examples provided.
vivid_cross_sell ~204
Suggest relevant, NON-pushy add-on products to round out a customer's order — 1–2 genuinely useful companions with a reason. PREFERS real frequently-bought-together data from Vivid Ads' order history (pass `product` = the product handle the customer chose); falls back to curated use-case bundles (pass `use_case`). Omit both to get guidance. Pass already_have to avoid re-suggesting what they've chosen. Never pressure — helpful suggestions only.
| Name | Type | Req | Description |
|---|---|---|---|
| already_have | array | — | product keys/handles the customer already chose (optional) — excluded from suggestions |
| product | string | — | the product handle the customer chose, e.g. 'pull-up-banners' — returns items frequently bought with it from real order history |
| use_case | string | — | curated fallback: 'trade-show', 'school-open-day', 'construction-fence', 'retail-promotion', 'real-estate', or 'corporate-conference' |
No output schema declared.
No examples provided.
vivid_delivery_estimate ~182
Estimate WHEN an order would arrive at an Australian postcode — the question behind 'can I get it by Friday?'. Works the timeline through honestly: production starts only after the customer approves their digital proof (3pm AEST cutoff), then production time for that product, then transit for their postcode (metro/regional/remote bands). Returns an arrival WINDOW plus the assumptions it made. This is an ESTIMATE, never a guarantee — always relay the caveat, and for a hard deadline tell them to call 1300 721 614. Free pickup from Derrimut VIC is usually the fastest option.
| Name | Type | Req | Description |
|---|---|---|---|
| artwork_ready | boolean | — | true if artwork is print-ready and the proof will be approved immediately |
| postcode | string | yes | 4-digit Australian delivery postcode |
| product | string | — | product name — used to read its real production time |
No output schema declared.
No examples provided.
vivid_delivery_quote ~221
EXACT delivery/freight cost to an Australian postcode for a product configuration — the SAME live rates the vividads.com.au checkout shows (carrier + shipping-rules apps; incl. GST). Use whenever the customer asks what shipping/delivery costs. Resolve the product + size/options + quantity first (vivid_product / vivid_price), then call with the postcode (suburb improves accuracy). Never estimate freight yourself. Always also mention free pickup from Derrimut VIC 3026.
| Name | Type | Req | Description |
|---|---|---|---|
| options | object | — | FULL selected options for option-rich/custom products (same shape as vivid_price.options) |
| postcode | string | yes | 4-digit Australian postcode |
| product | string | yes | product name, e.g. 'pull up banner' |
| quantity | number | — | — |
| size | string | — | (simple products) size, e.g. '850x2050' |
| state | string | — | VIC/NSW/QLD/SA/WA/TAS/NT/ACT (derived from postcode if omitted) |
| suburb | string | — | — |
No output schema declared.
No examples provided.
vivid_fulfilment_order_status ~186
Authoritative order state with a per-line-item breakdown and an order-level rollup. States: received, in_production, partially_ready, ready_for_pickup, dispatched, in_transit, out_for_delivery, delivered, completed, on_hold, cancelled. Includes the StarShipit shipping summary where available.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_email | string | yes | The email address on the order. REQUIRED for identity — order details are only returned when this email matches the order. The customer must give their email AND one of their order numbers. |
| line_item_id | string | — | Optional Shopify line item GID to scope to one item. |
| order_id | string | — | Shopify order GID, e.g. gid://shopify/Order/123. |
| order_name | string | — | Human order name, e.g. "#12345" (alias for order_id). |
No output schema declared.
No examples provided.
vivid_fulfilment_pickup_status ~152
Whether an order (or specific line items) is ready for pickup at Derrimut VIC — ready once printed and cut, before dispatch.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_email | string | yes | The email address on the order. REQUIRED for identity — order details are only returned when this email matches the order. The customer must give their email AND one of their order numbers. |
| line_item_id | string | — | Optional Shopify line item GID to scope to one item. |
| order_id | string | — | Shopify order GID, e.g. gid://shopify/Order/123. |
| order_name | string | — | Human order name, e.g. "#12345" (alias for order_id). |
No output schema declared.
No examples provided.
vivid_fulfilment_production_stage ~219
Where each line item is in production, per item plus a rollup. Stages (in order): received, in preflight, awaiting proof, proof approved, imposing, queued for print, sent to Caldera, printing, printed, at Zund cutter, cut, dispatched. Needs-action states: missing file, preflight failed, with design team, on hold (unpaid), proof rejected, duplicate. Each item also returns the press and the print timestamp.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_email | string | yes | The email address on the order. REQUIRED for identity — order details are only returned when this email matches the order. The customer must give their email AND one of their order numbers. |
| line_item_id | string | — | Optional Shopify line item GID to scope to one item. |
| order_id | string | — | Shopify order GID, e.g. gid://shopify/Order/123. |
| order_name | string | — | Human order name, e.g. "#12345" (alias for order_id). |
No output schema declared.
No examples provided.
vivid_fulfilment_shipping ~162
StarShipit shipping: carrier, tracking number, tracking URL, ETA and delivered flag. shipping_state: not_dispatched, shipped, in_transit, out_for_delivery, delivered, exception.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_email | string | yes | The email address on the order. REQUIRED for identity — order details are only returned when this email matches the order. The customer must give their email AND one of their order numbers. |
| line_item_id | string | — | Optional Shopify line item GID to scope to one item. |
| order_id | string | — | Shopify order GID, e.g. gid://shopify/Order/123. |
| order_name | string | — | Human order name, e.g. "#12345" (alias for order_id). |
No output schema declared.
No examples provided.
vivid_identity_start ~119
Start email verification before showing a customer's private data (past orders, reorder, saved address, email order-status). Sends a 6-digit code to the email. Returns a verificationId. Then ask the customer for the code and call vivid_identity_verify. Use this whenever a customer asks to see 'my orders', 'reorder', or 'status by email' and you don't already have a valid identity token.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | the customer's email to verify | |
| purpose | string | — | reorder | order_status | saved_details (optional) |
No output schema declared.
No examples provided.
vivid_identity_verify ~98
Complete email verification: pass the verificationId from vivid_identity_start and the 6-digit code the customer received. On success returns a short-lived identity token — pass that token to vivid_reorder / vivid_order_status to unlock the customer's private data. Codes expire in 10 minutes; attempts are limited.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | the 6-digit code the customer received by email |
| verificationId | string | yes | from vivid_identity_start |
No output schema declared.
No examples provided.
vivid_order_artwork ~166
Show a VERIFIED customer the PRINT-READY artwork files produced for one of their past orders (the actual files that went to print), so they can confirm them before reordering. Requires the order number and a valid identity token bound to the customer's email; only returns artwork for orders that belong to that customer. Returns view links to each print layout. Use when a customer asks 'what artwork did I print', 'show me my last print file', or before confirming a reorder.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | the customer's email (must match the identity token) | |
| order | string | yes | the order number to show artwork for, e.g. '117478' |
| token | string | — | the identity token from vivid_identity_verify (required — proves the customer owns this email/order) |
No output schema declared.
No examples provided.
vivid_order_status ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | — | alternatively, the customer's email to list recent orders (requires verified identity) | |
| reference | string | — | order # or quote/draft # (e.g. '#119581' or '#D776755') |
No output schema declared.
No examples provided.
vivid_place_order ~459
Create a Shopify DRAFT order for Vivid Ads team review — NOT a final/placed order, and NEVER charges a card. Before calling, summarise the exact product, quantity, configuration, verified price (if available), customer details, and delivery/pickup, then get the customer's explicit confirmation. Call WITHOUT confirm to get a Review summary; confirm:true only AFTER they confirm. Do NOT auto-retry after a timeout without first checking whether a draft was already created. Payment is a secure invoice/pay-link from the team; production waits on proof approval.
| Name | Type | Req | Description |
|---|---|---|---|
| artwork | object | — | { mode:'ai_design'|'upload_file'|'design_brief', designId?, imageUrl?, printPdfUrl?, fileUrl?, brief? } |
| company | string | — | — |
| confirm | boolean | — | set true ONLY after the customer reviews and confirms |
| customerType | string | — | retail|corporate|school|government|account — sets payment terms |
| delivery | object | — | pickup or delivery details. PICKUP: { method:'pickup', name, email, phone, pickupLocation?, notes? }. DELIVERY: { method:'delivery', name, email, phone, company?, address1, address2?, suburb, state,… |
| string | yes | — | |
| items | array | — | For a MULTI-LINE order (e.g. two banners with DIFFERENT designs): one entry per line, each { product, size?, options?, quantity?, artwork? }. Different designs must be SEPARATE entries (quantity 1 ea… |
| name | string | — | — |
| options | object | — | FULL selected options (same shape as vivid_price.options). Use vivid_product to see them. Prefer this over `size` for option-rich products. |
| phone | string | — | — |
| poNumber | string | — | — |
| product | string | — | — |
| quantity | number | — | — |
| size | string | — | — |
No output schema declared.
No examples provided.
vivid_price ~240
Calculate the current price for an EXACT product configuration. Pass `options` with the full selected configuration (use vivid_product first), or just `size` for simple products. Some products take several seconds or need manual confirmation. Before calling, briefly tell the customer you're checking the live price. Never estimate or reuse another configuration's price. When presenting, repeat the exact product title, quantity, dimensions, and price-affecting options.
| Name | Type | Req | Description |
|---|---|---|---|
| options | object | — | FULL selected options keyed by the schema keys from vivid_product, e.g. { size:'Medium', sides:'Double-sided', base:'Heavy Duty Metal Plate (5kg)' } or { size:'Custom', widthMm:700, heightMm:1000, ey… |
| product | string | yes | product name, e.g. 'pull up banner', 'corflute', 'a-frame', 'feather flag' |
| quantity | number | — | how many |
| size | string | — | (simple products) size, e.g. '850x2000', or a named size like 'medium' |
No output schema declared.
No examples provided.
vivid_price_breaks ~177
Vivid's REAL published volume price breaks for a product + size (e.g. 1 → $135 ea, 2 → $132.30, 5 → $128.25, 10 → $121.50 — save 10%). Use for bulk/trade pricing questions, or right after a price when a slightly larger quantity would save the customer money. Prices are AUD incl. GST and come from the same source as the live price, so they can never contradict a quote. If the product has no breaks it says so — never invent a discount.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | product name, e.g. 'premium pull up banner' |
| quantity | number | — | the customer's current quantity, to highlight the next worthwhile break |
| size | string | — | size — breaks are per size/variant |
No output schema declared.
No examples provided.
vivid_product ~163
Get a product's FULL real option schema (all dimensions, not just size) so you can configure it correctly before pricing/ordering. Returns each option's key, label, allowed values, default, whether it's required, whether it affects price, and display order — plus `turnaround` (the live production/lead time from the product page, e.g. 24 hours if artwork is approved by 3 pm AEST on a business day). Flags have Size/Printed Sides/Flag Base; corflute has Size (or custom W×H)/Eyelets/Cutting; table throws have Style/Size/Backside.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | product name, e.g. 'feather flag', 'corflute', 'table throw' |
No output schema declared.
No examples provided.
vivid_proof_status ~137
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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | the email address the order was placed under (required) | |
| order_number | string | yes | order number, e.g. '#121978' |
No output schema declared.
No examples provided.
vivid_recommend ~127
Recommend Vivid Ads signage for a goal + business type (real Australian signage: pull-up banners, A-frames, corflute, fabric banners, flags, media walls). Call with goal and business; omit either to get the next question to ask the customer.
| Name | Type | Req | Description |
|---|---|---|---|
| business | string | — | e.g. cafe-hospitality, retail, real-estate, events-expo, corporate, school, gym-fitness |
| goal | string | — | e.g. foot-traffic, promote-sale, stand-out-expo, advertise-outside, opening-store, brand-presence |
No output schema declared.
No examples provided.
vivid_reorder ~322
Reorder a customer's previous signage job — fast. Requires identity verification (emailed one-time code), not just an order number. action:'list' shows their past orders; action:'reorder' repeats one. ARTWORK: it reuses only the customer's previously APPROVED artwork (the print file), never a pre-approval upload; if it can't be confirmed automatically the team confirms it. A fresh proof is ALWAYS re-issued to confirm the artwork before printing. The customer may also supply new artwork or change the quantity. Re-prices with CURRENT pricing (never the old price). Creates a proof-gated draft order; never charges a card.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | — | 'list' (show past orders) or 'reorder' (repeat one) |
| artwork | string | — | new print-ready artwork file URL (optional; default = reuse previous) |
| confirm | boolean | — | set true to place the reorder (draft, proof-gated, never charges) |
| string | yes | the email the customer ordered under (required to find past orders) | |
| name | string | — | — |
| order | string | — | order name to reorder from, e.g. '#D12345' (optional) |
| product | string | — | which product to reorder, e.g. 'corflute' (optional; default = most recent eligible) |
| quantity | number | — | override quantity (optional; default = same as last time) |
| token | string | — | the identity token from vivid_identity_verify (required — proves the customer owns this email) |
No output schema declared.
No examples provided.
vivid_request_quote ~292
Email the customer a formal QUOTATION. If the exact configuration can be priced and an email is given, this INSTANTLY emails a branded PDF-style quotation (line items, GST, total, quote number, 14-day validity, accept-online link) — status 'quoted'. For custom/unpriceable products it logs the request for the team to prepare and send (status 'received'). Never takes payment. Confirm product, quantity, size/options, name, and email before submitting.
| Name | Type | Req | Description |
|---|---|---|---|
| artworkUrl | string | — | link to the customer's uploaded artwork (e.g. the fileUrl returned by vivid_upload_artwork), if any |
| company | string | — | — |
| design | string | — | design preference: 'ai_design' | 'upload_own' | 'design_later' |
| discountCode | string | — | any reseller/trade or discount code the customer mentioned (recorded, NOT applied here) |
| string | yes | — | |
| message | string | — | the customer's full request in their own words (multi-item OK) |
| name | string | — | — |
| options | object | — | FULL selected options (same shape as vivid_price.options) so the quotation is priced exactly — include size + any dropdowns/add-ons. |
| phone | string | — | customer phone (optional) |
| product | string | — | — |
| quantity | number | — | — |
| size | string | — | — |
No output schema declared.
No examples provided.
vivid_search ~173
Search the Vivid Ads catalogue by product name, category, or intended use (e.g. 'corflute', 'pull up banner', 'expo', 'shopfront'). Returns matching products grounded in Vivid's own Shopify collections, so it also surfaces same-range, same-purpose alternatives — products flagged `sameRange:true` come from the top match's curated collection (returned as `collection`). ALWAYS mention these to the customer (e.g. 'we have two Pull Up Banner options, and Fabric Banner Stands do the same job'). Treat a from-price as INDICATIVE only — use vivid_product for options then vivid_price for the exact configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | what the customer is looking for (a product name, a category, or a use-case like 'expo' or 'shopfront') |
No output schema declared.
No examples provided.
vivid_support_answer ~154
Answer a customer's support / FAQ question in Vivid Ads' voice, grounded in the team's real support history + verified policy. Covers turnaround & production time, digital proofs & approval, artwork specs & file setup, products & options, quotes & pricing, delivery & pickup, changing/cancelling orders, reorders, and the print guarantee. Returns the best-matching answer(s) and topic; if nothing matches it returns escalate:true so you can hand off to the team. Use for questions like 'how long does it take?', 'what file format do you need?', 'can I change my order?', 'where do I pick up?'.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | the customer's support question, in their own words |
No output schema declared.
No examples provided.
vivid_upload_artwork ~242
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. Optionally attaches the link to a quote, order, or design session. Accepts PDF / AI / EPS / JPG / PNG. Does NOT verify print-readiness — the team checks that. Use when a customer wants to send their print file via chat.
| Name | Type | Req | Description |
|---|---|---|---|
| contentBase64 | string | yes | the file contents, base64-encoded (data URI prefix OK). Small files only; for very large files share a download link instead. |
| string | — | customer email to associate with the upload (optional but recommended) | |
| filename | string | yes | original filename incl. extension, e.g. 'banner-artwork.pdf' |
| mimeType | string | — | MIME type, e.g. 'application/pdf' |
| orderId | string | — | associate with an order/draft (optional) |
| quoteId | string | — | associate with a quote request (optional) |
| sessionId | string | — | associate with a design session (optional) |
No output schema declared.
No examples provided.