Skip to main content
Glama

kling_generate_motion

Transfer motion from a reference video to a character image, animating a still photo by applying movements from the video.

Instructions

Transfer motion from a reference video to a character image.

This tool enables character animation by extracting motion from a video
and applying it to a static character image.

Use this when:
- You want to animate a character image using motion from a video
- You want to create a dance or movement video from a still photo
- You need to transfer specific movements to a character

Returns:
    Task ID and motion generation information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
image_urlYesURL of the character image to animate. The character in this image will be animated with the motion from the reference video.
video_urlYesURL of the reference video providing the motion. The character movements from this video will be transferred to the image.
character_orientationNoOrientation of the character. 'image' (default) uses the orientation from the character image, 'video' uses the orientation from the reference video.image
modeNoGeneration mode. 'std' (standard, default) for faster generation, 'pro' for higher quality.std
promptNoOptional text description to guide the motion transfer. Use to add details about the desired output.
keep_original_soundNoWhether to keep the original sound from the reference video. Options: 'yes' or 'no'. Default depends on API.
callback_urlNoWebhook callback URL for asynchronous notifications.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so description carries full burden. It mentions the operation (extract motion, apply to image) and return type (Task ID, motion generation info), but omits critical traits: asynchronous nature (implied by callback_url but not stated), permissions, rate limits, or whether input images/videos are stored temporarily. The 'pro' and '4k' modes hint at quality tiers but no cost/time trade-offs.

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?

Front-loaded with core purpose in first sentence. Three short paragraphs: purpose, use cases, returns. Efficient but could combine the returns line into the first paragraph. No wasted words.

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?

Given 7 parameters (2 required), 100% schema coverage, and an output schema (exists), the description adequately covers main behavior and parameter semantics. However, gaps remain: no explanation of how to retrieve the final output (though sibling tool kling_get_task exists), no mention of file size limits or supported formats, and the 'keep_original_sound' field is vague ('default depends on API').

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. Description adds value beyond schema: explains what 'character_orientation' values mean, that 'prompt' is optional for extra guidance, and that 'keep_original_sound' accepts 'yes'/'no'. Clarifies that 'callback_url' is for async notifications.

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 explicitly states 'Transfer motion from a reference video to a character image' with specific verb ('animate') and resource ('character image'). It clearly differentiates from siblings like kling_generate_video (raw video generation) and kling_generate_video_from_image (single image to video without motion reference).

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?

Provides a 'Use this when:' list with three explicit scenarios (animate character, create dance/movement, transfer specific movements). However, it lacks when-not-to-use guidance or comparisons to alternatives like kling_generate_video_from_image for simpler animations.

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