jimeng_visual_generation

generate_video

Generate videos from text, images, or multi-modal inputs including images, videos, and audio. Supports custom aspect ratios and resolutions.

Instructions

Create a video generation task using Volcengine API.

CRITICAL INSTRUCTIONS FOR AI AGENTS:

This tool ONLY submits the task. It returns a Task ID. You MUST subsequently call get_video_task_result in a loop (wait 5-10s between calls) to retrieve the actual video URL.
Use 'ratio' for video proportions (e.g., ratio="16:9"). DO NOT use 'size' or 'width'/'height'.
If user provides an Endpoint ID ('ep-...'), pass it to the 'model' parameter.

Capabilities:

Text-to-Video: Provide 'prompt' and 'ratio'.
Image-to-Video: Provide 'image_urls' array + optional 'prompt'.
Multi-Modal (Seedance 2.0): Mix 'image_urls' (up to 9), 'video_urls' (up to 3), and 'audio_urls' (up to 3).

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": {
      "params": "<params>"
    },
    "name": "generate_video"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Jul 13, 2026

TDQS

A5/5.0

Behavior5/5

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

Without annotations, the description fully discloses behavior: asynchronous (returns Task ID, needs polling), default values, accepted values for ratio and resolution, automatic role assignment for images, and model-specific limitations (e.g., generate_audio only for Pro models).

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?

Well-structured: starts with main purpose, then critical instructions in bold, followed by capabilities. Each sentence adds value without redundancy. Uses formatting for emphasis and lists for clarity.

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?

Fully covers all aspects needed for correct usage: explains the asynchronous workflow, all parameter constraints, mode-specific behaviors, and edge cases (e.g., seed for reproducibility, watermark option). With an output schema present, the description appropriately focuses on input semantics and process.

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?

Adds critical meaning beyond the input schema: clarifies that 'model' should be omitted unless user specifies an Endpoint ID, that 'ratio' must not use 'size' parameters, and explains the roles of image_urls, video_urls, and audio_urls for different modes. Enumerates accepted values for ratio explicitly.

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?

Explicitly states "Create a video generation task" and distinguishes from sibling tools by noting that this tool only submits the task and returns a Task ID, while `get_video_task_result` must be polled later.

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?

Provides clear when-to-use instructions: only for submitting tasks, not for retrieving results. Gives detailed do's and don'ts (e.g., use 'ratio' not 'size', leave 'model' empty unless custom endpoint). Lists three capability modes with their parameter requirements.

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

Deploy Server