Vadyu AI Video Ad Studio

vadyu_expand_video_funnel

One-call 0-credit 3-stage TOF/MOF/BOF funnel expansion for any completed Vadyu video (status === 'done'). Reuses the source video's verified 5s AI motion clip across all 3 vertical funnel recipes (ai_renders_reserved: 0, 0 AI render credits charged).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "video_id": "<video_id>"
    },
    "name": "vadyu_expand_video_funnel"
  }
}

Input Schema

Name	Required	Description
`theme`	No	Optional typography slate theme override ('dark' or 'light').
`format`	No	Optional aspect ratio override (default '9:16').
`cta_text`	No	Optional endcard CTA override (max 60 chars).
`video_id`	Yes	Numeric ID of a completed Vadyu video (`status === 'done'`) to expand into a 3-stage TOF/MOF/BOF funnel.
`logo_text`	No	Optional brand logo wordmark override (max 60 chars).
`audio_mood`	No	Optional audio mood override.
`brand_text`	No	Optional brand headline override (max 120 chars).
`brand_subtext`	No	Optional brand subtext override (max 120 chars).
`campaign_preset`	No	Optional 3-stage campaign funnel preset ID (auto-detected from the video's vertical across all 33 presets when omitted).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026

changedInput schema / properties / campaign_preset / description

Previous value: -"Optional 3-stage campaign funnel preset ID (auto-detected from the video's vertical across all 32 presets when omitted)."New value: +"Optional 3-stage campaign funnel preset ID (auto-detected from the video's vertical across all 33 presets when omitted)."

AddedNov 1, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description does real work: it discloses cost behavior ('0-credit', `ai_renders_reserved: 0`) and that the source clip's motion asset is reused across all 3 recipes, which an agent could not infer from the schema. It stops short of describing what is created/returned (e.g., IDs of the three funnel items) or failure behavior, leaving real gaps for a mutation tool.

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?

Two dense sentences, front-loaded with the core action and scope, and every clause carries information. Slight cost from jargon-dense phrasing (`ai_renders_reserved: 0`) that reads like a schema field repeated back.

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

Completeness3/5

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

For a 9-parameter mutation tool with no output schema and no annotations, the description covers cost and reuse but never says what the call produces (three new funnel videos? recipe IDs?) or how the auto-detected campaign_preset behaves on completion. An agent knows when to call it but not what it gets back.

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%, so all 9 parameters including enums and the optional overrides are already documented. The description adds only the funnel-level context (3 stages, reuse of the motion clip), not field-level meaning, 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 ('expand ... funnel') with precise scope: 3-stage TOF/MOF/BOF for any completed Vadyu video. The `status === 'done'` precondition and 'one-call' framing let an agent distinguish it from vadyu_generate_video_ad and vadyu_list_recipes without opening a schema.

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 a clear trigger condition (a video with `status === 'done'`) and clarifies the economics that motivate choosing it (0 credits, reuses existing motion clip). It does not name a sibling as the alternative or state when to prefer vadyu_generate_video_ad instead, so no explicit exclusion guidance.

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

All Vadyu AI Video Ad Studio 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.