Skip to main content
Glama
veniceai

Venice MCP Server

Official
by veniceai

Venice Video Queue

venice_video_generate

Queue video generation using AI models like Veo 3.1, Kling, Wan, and more. Supports text, image, video, and audio inputs with NSFW prompts.

Instructions

Queue a video generation. Supports Sora 2, Veo 3.1, Kling, Wan, LTX 2, Seedance, Runway Gen-4, and others. Pick a specific id like "veo3.1-fast-text-to-video", "veo3.1-fast-image-to-video", "kling-2.6-pro-text-to-video", "wan-2.6-text-to-video", "seedance-2-0-r2v" etc. Uncensored: NSFW prompts allowed where the model permits. Supports x402 wallet auth (no Venice account needed) and API key. Returns { model, queue_id }; poll with venice_video_status. NOTE: 'duration' is a string enum like '4s' / '6s' / '8s' (model-specific, see model card).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedNo
audioNoEnable or disable audio generation for models that support it. Defaults to true.
modelYesRequired. Full model id, e.g. "veo3.1-fast-text-to-video".
promptYes
durationNoDuration as model-specific string enum, e.g. "4s", "6s", "8s". See GET /v1/models/:id/card.
elementsNoFor Kling O3 R2V and similar: up to 4 character/object elements. Reference in prompt as @Element1, @Element2, etc.
audio_urlNoFor models that support audio input: background music. URL or data URL. Supported: WAV, MP3. Max 30s, 15MB.
image_urlNoFor image-to-video models: starting frame. URL or data URL.
video_urlNoFor video-to-video models (e.g. seedance-2-0-r2v): input video. URL or data URL. Supported: MP4, MOV, WebM.
resolutionNoOutput resolution, e.g. "720p", "1080p", "4k". Model-specific; see model card.
aspect_ratioNo
end_image_urlNoFor models that support end frames or transitions. URL or data URL.
upscale_factorNoFor upscale models only: 1 = quality enhance, 2 = double resolution, 4 = quadruple.
negative_promptNoNegative prompt (what to avoid). Supported by Seedance and other models.
scene_image_urlsNoFor models with advanced element support: up to 4 scene reference images. Reference in prompt as @Image1, @Image2, etc.
reference_audio_urlsNoFor Seedance 2.0 R2V and similar: up to 3 reference audio clips for vocal timbre, narration, or sound effects. Per-clip 2–15s, WAV/MP3; aggregate ≤15s. Must be paired with at least one reference image or video. Each a URL or data URL.
reference_image_urlsNoFor models with reference image support: up to 9 images for character/style consistency. Each a URL or data URL.
reference_video_urlsNoFor Seedance 2.0 R2V and similar: up to 3 reference video clips to inherit subject motion, camera movement, and style. Per-clip 2–15s, MP4/MOV, ≤50MB; aggregate ≤15s. Each a URL or data URL.
Behavior4/5

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

The description discloses key behaviors: return format (model, queue_id), uncensored nature, auth methods, and duration enum. With no annotations, it carries the full burden and does so well, though it omits latency, quotas, or queuing specifics.

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?

The description is front-loaded with purpose, efficiently uses each sentence to add value (model list, auth, return, duration note), and avoids redundancy with the schema.

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?

Given 18 parameters, high schema coverage, and no output schema, the description provides substantial context on purpose and parameters. However, it lacks completeness on error handling, queue behavior, and status polling details, which would enhance practical use.

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

Parameters5/5

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

With 83% schema coverage, the description compensates by adding concrete examples (model IDs like 'veo3.1-fast-text-to-video'), usage syntax ('@Element1'), and format details ('URL or data URL', '4s/6s/8s') that the schema lacks.

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 'Queue a video generation' with a specific verb and resource. It lists supported models and explicitly distinguishes itself from sibling 'venice_video_status' by mentioning polling with that tool.

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?

The description indicates when to use this tool (asynchronous generation) and implicitly contrasts with status polling. However, it does not explicitly compare to sibling 'venice_video_complete' or provide guidelines on model selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/veniceai/venice-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server