Skip to main content
Glama
runapi-ai

kling-mcp

by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_task

Poll a Kling task by task ID and action to retrieve its current status and latest result payload.

Instructions

Fetch the current status and latest result payload for a kling task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAsynchronous endpoint the task was created on.
task_idYesTask id returned when the task was created.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "ai_avatar",
-  "extend_video",
-  "image_to_video",
-  "motion_control",
-  "text_to_video"
-]New value: +[
+  "ai_avatar",
+  "edit_video",
+  "extend_video",
+  "image_to_video",
+  "motion_control",
+  "text_to_video"
+]
  3. Changed2 schema fields changedv0.1.13
    • changedInput schema / properties / action / description
      Previous value: -"Endpoint the task was created on."New value: +"Asynchronous endpoint the task was created on."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "ai_avatar",
-  "image_to_video",
-  "motion_control",
-  "text_to_video"
-]New value: +[
+  "ai_avatar",
+  "extend_video",
+  "image_to_video",
+  "motion_control",
+  "text_to_video"
+]
  4. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does add real behavioral context by implying read-only retrieval and that the result is the 'latest' payload (i.e., may not yet be final), which supports polling semantics. It does not disclose rate limits, how to interpret status values, or what happens on an unknown task_id.

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?

A single front-loaded sentence with no filler; the resource and the returned payload are stated immediately.

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?

For a simple two-parameter lookup with full schema coverage and no output schema, the description usefully states what comes back (status plus latest result payload), which compensates for the missing output schema. It stops short of explaining status semantics or error behavior, so it is not fully complete.

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%, and both required parameters (task_id, action enum) are documented in the schema. The description adds no further parameter detail, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Fetch') and resource ('status and latest result payload for a kling task'), so the agent knows exactly what it retrieves. It is clearly distinguishable from the sibling creation tools (text_to_video, extend_video, etc.), though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: because siblings all create tasks, this tool is obviously the status/polling counterpart, and the word 'current' hints at repeated polling. However, there is no explicit statement of when to call it (e.g., after task creation, poll until terminal status) or any exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools