vivideo

create_auto_video

Create a video in AUTO mode: Vivideo writes the script and produces a complete AI-avatar video from your prompt. Returns immediately with a video id and status "processing" (paid) or "preview" (free accounts — see the preview field and upgrade link). Then call wait_for_video or get_video. An Idempotency-Key is sent automatically so a retry never creates a duplicate. Rendering requires a premium plan and credits.

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": {
      "prompt": "<prompt>"
    },
    "name": "create_auto_video"
  }
}

Input Schema

Name	Required	Description
`name`	No
`prompt`	Yes	What the video should show or say.
`voice_id`	No	From list_voices.
`avatar_id`	No	From list_avatars. Omit for a default presenter.
`folder_id`	No
`orientation`	No
`brand_kit_id`	No	A brand_ref from list_brand_kits.
`idempotency_key`	No	Optional. Reuse the same key to make a retry safe.
`duration_seconds`	No	5–300, default 30.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Discloses key behaviors: async return with video id and status ('processing' vs 'preview'), automatic idempotency-key handling, and rendering requiring premium plan and credits. No annotations provided, so description carries full burden and handles it well.

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?

Efficient three-sentence description that front-loads the core action. Each sentence adds value, though a bullet structure could improve readability for the workflow details.

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

Completeness4/5

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

Covers the async nature, plan restrictions, next steps, and idempotency. Missing parameter details and error handling, but given the complexity and lack of output schema, it provides a solid overview.

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 67%, and the description adds minimal new parameter context beyond the schema (e.g., brand_kit_id from list_brand_kits). It does not explain folder_id, name, or orientation, which remain undocumented.

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?

The description clearly states it creates a video in AUTO mode where Vivideo handles scripting and production. It distinguishes from manual mode via sibling context and uses specific verbs ('creates', 'returns', 'call').

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?

Provides clear when-to-use context: for fully automatic video generation from a prompt. Mentions next steps (call wait_for_video or get_video) and plan requirements, but does not explicitly exclude scenarios or mention alternatives beyond the sibling list.

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

All vivideo 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.