Skip to main content
Glama

kling_extend_video

Extend existing videos by generating additional content to continue motion and storylines. Build longer sequences piece by piece from short clips using text prompts.

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) or 'pro' (higher quality).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?

With no annotations provided, the description carries the full burden. It successfully conveys that the tool appends content temporally ('after the original video ends') and mentions 'Task ID' in returns, hinting at async behavior. However, it fails to explain the async workflow (e.g., need to poll with kling_get_task), preservation of the original video, or any rate/cost implications.

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?

Well-structured with clear sections: purpose statement, elaboration, usage guidelines, and returns. The 'Use this when' bullets efficiently convey intent. Slightly redundant in mentioning returns when output schema exists, but appropriately front-loaded and free of 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 100% schema coverage and existence of output schema, the description adequately covers the tool's purpose and selection criteria. Minor gap in not referencing the sibling kling_get_task tool for polling the returned Task ID, but sufficient for agent selection and invocation.

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%, with comprehensive documentation for all 6 parameters including enums and defaults. The description does not explicitly discuss parameters, relying entirely on the schema. With such high schema coverage, the baseline score of 3 is appropriate.

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 ('Extend') and resource ('existing video'), clearly defining scope as 'additional content' that continues 'after the original video ends.' This effectively distinguishes it from sibling generation tools like kling_generate_video by emphasizing 'previously generated' and 'continue.'

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?

Includes an explicit 'Use this when:' section with three concrete scenarios (video too short, continue story/motion, building longer video piece by piece). This provides clear guidance on when to select this tool over initial generation alternatives.

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