Skip to main content
Glama

seedance_generate_video_from_image

Generate AI video from an image by animating the first frame, transitioning to a last frame, or using reference images for style guidance.

Instructions

Generate AI video using reference images with ByteDance Seedance.

This allows you to control the video by specifying first frame, last frame,
or reference images. Seedance will generate smooth motion based on the inputs.

Use this when:
- You have a specific image you want to animate
- You want to create a video transition between two images
- You need style guidance from reference images
- You need precise control over the video's visual content

Note: reference_image_urls cannot be combined with first_frame_url/last_frame_url.
At least one image input must be provided.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesDescription of the video motion and content. Describe what should happen in the video, how objects should move, what transitions to include.
first_frame_urlNoURL of the image to use as the first frame of the video. The video will animate from this image. Supports https:// URLs or base64 data:image/... URIs.
last_frame_urlNoURL of the image to use as the last frame of the video. The video will animate towards this image. Supports https:// URLs or base64 data:image/... URIs.
reference_image_urlsNoList of reference image URLs for style/content guidance. These images influence the look but are not used as frames. Cannot be combined with first_frame_url or last_frame_url.
modelNoModel version to use. Use 'doubao-seedance-2-0-260128' for latest generation quality, 'doubao-seedance-2-0-fast-260128' for latest generation speed, For image-to-video, consider 'doubao-seedance-1-0-lite-i2v-250428' for lightweight I2V, or any Pro model for higher quality.doubao-seedance-1-0-pro-250528
resolutionNoVideo resolution. Options: '480p', '720p', '1080p'.720p
ratioNoVideo aspect ratio. Use 'adaptive' to match your input image ratio.16:9
durationNoVideo duration in seconds. Range: 2-12. Default is 5. Mutually exclusive with 'frames'.
framesNoFrame count for the generated video. Must satisfy 25+4n (e.g. 29, 33, 37, ..., 289). Mutually exclusive with 'duration'.
generate_audioNoIf true, generate audio. Only supported by 1.5 Pro model. Default is false.
service_tierNoService tier. 'default' or 'flex' (50%% cheaper). Default is 'default'.default
seedNoRandom seed. -1 for random. Default is -1.
return_last_frameNoIf true, return the last frame of the generated video. Default is false.
callback_urlNoWebhook callback URL for asynchronous notifications.
execution_expires_afterNoTask timeout threshold in seconds. Default is 172800 (48 hours).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions constraints on image input combinations, but lacks details on asynchronous behavior, task polling, failure modes, or typical generation time. The return value indicates a 'Task ID' implying async, but this is not elaborated.

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 well-structured with a clear purpose statement, bullet-pointed use cases, and a final note on constraints and returns. It is slightly verbose but front-loaded with key information. Every section serves a purpose.

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 the tool's complexity (15 parameters, 1 required, output schema exists), the description covers core concepts, use cases, and constraints. It explains the interplay of image inputs and the trade-off between duration and frames. Missing async details are a minor gap but overall adequate.

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 baseline is 3. The description adds context by grouping image inputs and explaining their roles, but the schema already provides clear descriptions for each parameter. The added value is marginal.

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 generates AI video using reference images, distinguishing it from sibling tools like seedance_generate_video which likely uses text-only input. The verb 'generate' and resource 'video from image' are specific and unambiguous.

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 lists specific scenarios for use (animating images, creating transitions, style guidance). It also notes when not to combine inputs (reference_image_urls vs first/last frame). However, it does not explicitly state when to prefer seedance_generate_video over this tool, missing a direct contrast with the sibling.

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

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