Skip to main content
Glama
AceDataCloud

KlingMCP

by AceDataCloud
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
Python
Hybrid

kling_extend_video

Extend a generated video by adding a described continuation after the original ends. Provide the video ID and prompt for the new motion to create a longer clip.

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
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-v1
promptYesDescription of what should happen in the extended portion of the video. Describe the continuation of motion and new content.
durationNoDuration of the extended segment in seconds. Supports 5 or 10.
video_idYesID of the video to extend. This is the 'video_id' field from a previous generation result.
cfg_scaleNoClassifier-free guidance scale.
callback_urlNoOptional webhook URL for asynchronous result notification.
negative_promptNoThings to avoid in the extended video.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.1.23
    • addedInput schema / properties / callback_url
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional webhook URL for asynchronous result notification.",
+  "title": "Callback Url"
+}
  2. Changed1 schema field changedv0.1.21
    • changedInput schema / properties / model / default
      Previous value: -"kling-v2-master"New value: +"kling-v1"
  3. Changed1 schema field changedv0.1.18
    • changedInput schema / properties / model / enum
      Previous value: -[
-  "kling-v1",
-  "kling-v1-6",
-  "kling-v2-master",
-  "kling-v2-1-master",
-  "kling-v2-5-turbo",
-  "kling-v2-6",
-  "kling-v3",
-  "kling-v3-omni",
-  "kling-video-o1"
-]New value: +[
+  "kling-v1",
+  "kling-v1-6",
+  "kling-v2-master",
+  "kling-v2-1-master",
+  "kling-v2-5-turbo",
+  "kling-v2-6",
+  "kling-v3",
+  "kling-v3-omni",
+  "kling-o1"
+]
  4. Changed1 schema field changedv0.1.17
    • addedInput schema / properties / duration
      Added value: +{
+  "default": 5,
+  "description": "Duration of the extended segment in seconds. Supports 5 or 10.",
+  "title": "Duration",
+  "type": "integer"
+}
  5. Changed2 schema fields changedv0.1.13
    • changedInput schema / properties / mode / description
      Previous value: -"Generation mode. 'std' (standard, default) or 'pro' (higher quality)."New value: +"Generation mode. 'std' (standard, default), 'pro' (higher quality), or '4k' (native 4K, only for kling-v3 and kling-v3-omni)."
    • changedInput schema / properties / mode / enum
      Previous value: -[
-  "std",
-  "pro"
-]New value: +[
+  "std",
+  "pro",
+  "4k"
+]
  6. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / model / enum
      Previous value: -[
-  "kling-v1",
-  "kling-v1-6",
-  "kling-v2-master",
-  "kling-v2-1-master",
-  "kling-v2-5-turbo",
-  "kling-video-o1"
-]New value: +[
+  "kling-v1",
+  "kling-v1-6",
+  "kling-v2-master",
+  "kling-v2-1-master",
+  "kling-v2-5-turbo",
+  "kling-v2-6",
+  "kling-v3",
+  "kling-v3-omni",
+  "kling-video-o1"
+]
  7. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are supplied, so the description must disclose behavior. It reveals an extension returns a Task ID and extended video info, implying an asynchronous workflow, but does not state that results must be polled via get_task, whether the original video is modified, or any required permissions/billing. The continuation semantics are clear, but operational behavior is under-specified.

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?

Information is front-loaded with a one-sentence summary and scannable bullets. Minor redundancy between the first sentences ('Extend... additional content' vs 'continue... adding more motion and content') costs a point.

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?

For an 8-parameter tool with no annotations, the description covers the core use case and return value but omits the asynchronous task lifecycle (how to retrieve the result, whether to use callback_url) despite siblings like kling_get_task existing. Schema covers parameter semantics, so the remaining gap is moderate.

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?

Input schema descriptions cover 100% of parameters, including defaults and enum semantics for mode/model and the source of video_id. The prose description adds nothing beyond the schema—it restates the prompt guidance already in the schema—so baseline 3 is warranted.

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?

Clearly states the verb ('extend') and resource ('an existing video'), and explains the result is continued content after the original ends. This differentiates it from generation siblings like kling_generate_video and kling_generate_motion.

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 an explicit 'Use this when' bullet list with three concrete scenarios. Does not name alternatives or exclude cases, so it misses the when-not dimension, but the positive triggers are unambiguous.

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