Skip to main content
Glama

kling_generate_video_from_image

Generate a video from a reference start image, optionally providing an end image to create a smooth motion transition.

Instructions

Generate AI video using reference images as start and/or end frames.

This allows you to control the video by specifying what the first frame
and/or last frame should look like. Kling will generate smooth motion between them.

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

start_image_url is required. end_image_url is optional.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoGeneration mode. 'std' (standard, default), 'pro' (higher quality), or '4k' (native 4K, only for kling-v3 and kling-v3-omni).std
modelNoKling model to use. Default: 'kling-v2-master'.kling-v2-master
promptYesDescription of the video motion and content. Describe what should happen in the video, how objects should move, what transitions to include.
timeoutNoTimeout in seconds for the API to return data. Default is 300.
durationNoVideo duration in seconds. kling-v3/kling-v3-omni: 3-15; kling-o1: 5 only; other models: 5 or 10.
cfg_scaleNoClassifier-free guidance scale from 0 to 1. Not supported by Omni generation.
image_listNoAdditional Omni reference images for kling-o1 or kling-v3-omni. Do not set type='first_frame' or 'end_frame' when the same frame is already supplied through start_image_url or end_image_url.
video_listNoOne Omni reference video for kling-o1 or kling-v3-omni.
aspect_ratioNoVideo aspect ratio. Usually should match your input image ratio.16:9
callback_urlNoWebhook callback URL for asynchronous notifications.
end_image_urlNoURL of the image to use as the last frame of the video. The video will animate towards this image.
camera_controlNoStructured camera control. Not supported by Omni generation.
generate_audioNoWhether to generate audio synchronously. Supported by kling-v3, kling-v3-omni, and kling-v2-6 (pro mode only).
negative_promptNoThings to avoid in the video.
start_image_urlNoRequired URL of the image to use as the first frame of the video.

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 bears the full burden. It explains that Kling generates smooth motion between frames and returns a task ID with video info. However, it does not disclose async behavior, error handling, or rate limits, leaving some behavioral gaps.

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 paragraphs and bullet points, but it repeats 'start_image_url is required. end_image_url is optional.' in two places. Otherwise, it is concise and front-loaded.

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?

While the description covers the main purpose and usage scenarios, it lacks details about polling, error codes, or constraints like file size. Given the complexity (15 parameters) and existence of an output schema, more context would be helpful.

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 value by stating that start_image_url is required and end_image_url is optional, but contradicts the schema (which only requires prompt). This slight inconsistency reduces the score.

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 'Generate AI video using reference images as start and/or end frames.' This is a specific verb-resource description that distinguishes this tool from siblings like kling_generate_video (text-to-video) and kling_extend_video.

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 includes a bullet list of explicit use cases (e.g., 'You have a specific image you want to animate'). It does not explicitly contrast with sibling tools, but the context is clear enough for an AI agent to decide when to use this tool.

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/KlingMCP'

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