Skip to main content
Glama

kling_extend_video

Extend a short AI-generated video by adding more motion and content after the original ends. Describe the continuation to build longer video sequences.

Instructions

Extend an existing video with additional content.

This allows you to continue a previously generated video, adding more motion
and content after the original video ends.

Use this when:
- A generated video is too short and you want to add more
- You want to continue the story or motion from a previous video
- You're building a longer video piece by piece

Returns:
    Task ID and the extended video information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
video_idYesID of the video to extend. This is the 'video_id' field from a previous generation result.
promptYesDescription of what should happen in the extended portion of the video. Describe the continuation of motion and new content.
modelNoKling model to use. Default: 'kling-v2-master'.kling-v2-master
modeNoGeneration mode. 'std' (standard, default), 'pro' (higher quality), or '4k' (native 4K, only for kling-v3 and kling-v3-omni).std
negative_promptNoThings to avoid in the extended video.
cfg_scaleNoClassifier-free guidance scale.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided; description only states functionality without disclosing behavioral traits like permission requirements, rate limits, or effects on original video. It implies mutation but lacks detail beyond purpose.

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?

Extremely concise, uses bullet points for clarity, and front-loads the main action. Every sentence provides value without repetition or fluff.

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 presence of an output schema (per context signal) and full parameter descriptions, the description adequately explains return value. However, lacks any prerequisites, error handling, or behavioral nuances that might be needed for a complete understanding.

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 the description adds no new meaning to parameters beyond what is already in the schema. It repeats the overall purpose but does not enhance parameter understanding.

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 the verb 'extend' and resource 'existing video', and distinguishes from generate tools. 'Extend an existing video with additional content' is 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?

Explicitly lists three use cases in bullet points (when video too short, continue story, build longer piece). Does not explicitly mention when not to use or alternatives, but context of sibling tools implies it is for continuation, not new generation.

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