Vendo AI

Preview launching a campaign

preview_launch_campaign

Readiness report for launch/resume — NOTHING IS SENT: ready flag, blockers (AGENT_REQUIRED, AUDIENCE_REQUIRED, AUDIENCE_EMPTY (0 contacts), CLIENT_MAILBOX_NOT_CONNECTED, PAID_PLAN_REQUIRED for Vendo managed senders, INVALID_STATUS), warnings, real recipient count, channels, daily email/LinkedIn limits, sender mode, email steps, schedule and the LinkedIn accounts that will be activated. ALWAYS call this first and show the result to the user before launch_campaign.

Input Schema

Name	Required	Description	Default
`id`	Yes	Campaign id (UUID) from list_campaigns
`linkedin_account_ids`	No	Override which LinkedIn accounts get activated (default: settings.selectedLinkedinAccountIds, else all connected)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

addedInput schema / properties / id / description

Added value: +"Campaign id (UUID) from list_campaigns"

addedInput schema / properties / linkedin_account_ids

Added value: +{
+  "description": "Override which LinkedIn accounts get activated (default: settings.selectedLinkedinAccountIds, else all connected)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

First observedJul 28, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description carries full burden and does so: 'NOTHING IS SENT' discloses no side effects, and it enumerates the blocker codes (AGENT_REQUIRED, PAID_PLAN_REQUIRED, etc.) and returned fields, giving the agent rich behavioral context.

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?

Front-loads the key fact ('NOTHING IS SENT') immediately, then the enumerations follow. Dense but every clause earns its place given the tool's complexity.

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?

Despite no output schema, the description enumerates the return contents (ready flag, blockers, warnings, recipient count, channels, limits, sender mode, schedule, LinkedIn accounts), leaving an agent fully informed.

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 coverage is 100%, so both parameters (id, linkedin_account_ids) are already documented in the schema. The description adds no syntax or format details beyond what the schema provides, so 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 and resource: 'Readiness report for launch/resume'. It clearly distinguishes itself from the mutating sibling launch_campaign by emphasizing the preview/dry-run nature.

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?

Explicitly says 'ALWAYS call this first and show the result to the user before launch_campaign', naming the alternative and the condition that selects it. No inference required.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Vendo AI 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?