Skip to main content
Glama

seedance_generate_video

Turn any text prompt into an AI-generated video clip. Describe the scene, motion, style, or mood to create a video with URLs and metadata, no reference images required.

Instructions

Generate AI video from a text prompt using ByteDance Seedance.

This is the simplest way to create video - just describe what you want and
Seedance will generate a high-quality AI video.

Use this when:
- You want to create a video from a text description
- You don't have reference images
- You want quick text-to-video generation

For using reference images (first/last frame, reference), use
seedance_generate_video_from_image instead.

Returns:
    Task ID and generated video information including URLs and metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedNoRandom seed for reproducible generation. Range: -1 to 4294967295. Use -1 for random. Default is -1.
modelNoModel version to use. Options: 'doubao-seedance-2-5-260628' (latest flagship, up to 30 seconds, multimodal reference, edit/extend, default), 'doubao-seedance-2-0-260128' (highest resolution, supports 4k), 'doubao-seedance-2-0-fast-260128' (latest generation, faster, up to 720p), 'doubao-seedance-2-0-mini-260615' (latest generation, lightweight, cheapest within the 2.0 series, up to 720p), 'doubao-seedance-1-5-pro-251215' (1.5 flagship, supports audio), 'doubao-seedance-1-0-pro-250528' (1.0 standard), 'doubao-seedance-1-0-pro-fast-251015' (1.0 fast, cost-optimized), 'doubao-seedance-1-0-lite-t2v-250428' (lightweight text-to-video), 'doubao-seedance-1-0-lite-i2v-250428' (lightweight image-to-video).doubao-seedance-2-0-260128
ratioNoVideo aspect ratio. Options: '16:9' (landscape, default), '9:16' (portrait), '1:1' (square), '4:3', '3:4', '21:9' (ultrawide), 'adaptive'.16:9
toolsNoOptional Seedance 2.5 web search tool configuration.
framesNoFrame count for the generated video (1.0 series only). Must satisfy 25+4n (e.g. 29, 33, 37, ..., 289). Mutually exclusive with 'duration'.
promptYesDescription of the video to generate. Max 1000 characters. Be descriptive about the scene, motion, style, and mood. You can also include inline parameters like '--rs 720p --rt 16:9 --dur 5'. Examples: 'A cat walking through a garden with butterflies', 'Cinematic aerial shot of mountains at sunset'
durationNoVideo duration in seconds. 1.0 series: 2–12; 1.5 Pro: 4–12; 2.0 series: 4–15; 2.5: 4–30. Use -1 for auto-duration (1.5 Pro and 2.x). Default is 5. Mutually exclusive with 'frames'.
priorityNoSeedance 2.5 task priority from 0 to 9.
watermarkNoIf true, add a watermark to the video. Default is false.
resolutionNoVideo resolution. Options: '480p', '720p' (default), '1080p', '4k'. '4k' is supported only by 'doubao-seedance-2-0-260128'; '2-5' maxes out at '1080p'; '2-0-fast' and '2-0-mini' max out at '720p'.720p
callback_urlNoWebhook callback URL for asynchronous notifications. When provided, the API returns immediately with a task_id and calls this URL when the video is generated.
camera_fixedNoIf true, keep the camera fixed during generation. Default is false.
output_formatNoSeedance 2.5 output format: mp4 or mov.
generate_audioNoIf true, generate audio along with the video. Supported by 'doubao-seedance-1-5-pro-251215' and the 'doubao-seedance-2-0' series; other models ignore it. Approximately doubles the cost. Default is false.
return_last_frameNoIf true, also return the last frame of the generated video as an image URL. Useful for video extension workflows. Default is false.
safety_identifierNoStable anonymous end-user identifier. Do not use personal information.
execution_expires_afterNoTask timeout threshold in seconds. Default is 172800 (48 hours).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Install Server

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does add a Returns clause mentioning task ID, video URLs, and metadata, which hints at task-based behavior. However, it omits important operational traits such as generation taking significant time and the likely need to poll or wait for the final video.

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?

The description is compact and front-loaded: action, use cases, alternative, and return summary come in a readable order. The 'simplest way / high-quality' sentence is slightly promotional and redundant with the first sentence, but it does not meaningfully inflate the length.

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 17-parameter tool, the input schema covers most details and an output schema presumably documents return structure. The description covers primary use cases and sibling routing, but it does not explain how to retrieve the final result, e.g., via seedance_get_task, or warn about long-running generation. It is adequate but has clear gaps.

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%, and the schema already documents all 17 parameters with defaults, enums, and model-specific constraints. The description adds little beyond identifying the prompt as the core input and clarifying this is the text-only variant, so the parameter burden is adequately carried by the schema.

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 opens with a specific verb and resource: 'Generate AI video from a text prompt using ByteDance Seedance.' It also names the sibling seedance_generate_video_from_image, so an agent can immediately distinguish text-to-video generation from image-conditioned generation.

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?

The 'Use this when' bullets clearly define the conditions: creating video from text, no reference images, and quick text-to-video generation. It explicitly directs image-reference workflows to seedance_generate_video_from_image instead, which is excellent routing guidance.

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

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/AceDataCloud/SeedanceMCP'

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