vivid-ads-commerce

Recommend signage

vivid_recommend

Read-onlyIdempotent

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.

Input Schema

Name	Required	Description	Default
`goal`	No	e.g. foot-traffic, promote-sale, stand-out-expo, advertise-outside, opening-store, brand-presence
`business`	No	e.g. cafe-hospitality, retail, real-estate, events-expo, corporate, school, gym-fitness

Output Schema

Name	Required	Description
`status`	Yes	outcome discriminator, e.g. ok / priced / need_size / manual_quote / unknown_product / error
`message`	No
`options`	No
`products`	No
`question`	No
`agent_note`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "agent_note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "message": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "options": {},
+    "products": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "from": {
+            "description": "indicative from-price, AUD incl. GST — NOT a configured price"
+          },
+          "name": {
+            "description": "product title"
+          },
+          "product": {
+            "description": "product handle — pass to vivid_product / vivid_price"
+          },
+          "reason": {
+            "description": "why it matched"
+          },
+          "sameRange": {
+            "description": "true = same-range alternative from the top match's collection"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "question": {},
+    "status": {
+      "description": "outcome discriminator, e.g. ok / priced / need_size / manual_quote / unknown_product / error",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": "object"
+}

First observedJul 19, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds a genuine behavioral trait beyond that: omitting either parameter returns the next question to ask the customer, revealing a conversational fallback mode. It does not describe return payload shape, but an output schema exists.

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?

Two sentences, zero waste: purpose and product scope first, then the calling/omission rule. Front-loaded and every clause earns its place.

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 an output schema handling return values and annotations covering safety and idempotency, the description needs only to state purpose, inputs and the fallback behavior, all of which it does. Nothing required to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both parameters carry example values, so the schema does the heavy lifting. The description only restates that goal and business are the inputs and adds the omission behavior, contributing nothing about format or accepted values beyond the schema. Baseline 3 applies.

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 ('Recommend') plus resource ('Vivid Ads signage'), scoped by goal + business type. It names concrete product families (pull-up banners, A-frames, corflute, fabric banners, flags, media walls), which distinguishes it from generic siblings like vivid_product or vivid_cross_sell without opening their schemas.

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?

Gives explicit calling guidance ('Call with goal and business; omit either to get the next question to ask the customer'), which tells the agent how and when to invoke it. It stops short of naming alternatives (e.g. vivid_cross_sell or vivid_price) or stating when NOT to use it, so it is clear context rather than full routing.

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?