kling-mcp

check_pricing

Look up RunAPI pricing for Kling AI video and avatar models to verify costs before starting generation tasks.

Instructions

Look up RunAPI pricing for the kling model line.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`model`	No	Model slug. Defaults to the line's primary model.
`action`	No	Endpoint name. Defaults to the endpoint that offers the model.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.0Oct 1, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

removedInput schema / properties / model / enum

Removed value: -[
-  "kling-ai-avatar-pro",
-  "kling-ai-avatar-standard",
-  "kling-ai-avatar-v1-pro",
-  "kling-v1-avatar-standard",
-  "kling-v3-omni-edit",
-  "kling-v3-omni-reference",
-  "kling-v2.5-turbo-image-to-video-pro",
-  "kling-v2.5-turbo-text-to-video-pro",
-  "kling-o1",
-  "kling-v2.1-master-image-to-video",
-  "kling-v2.1-pro",
-  "kling-v2.1-standard",
-  "kling-v2.6",
-  "kling-v3-omni",
-  "kling-v3-turbo-image-to-video",
-  "kling-3.0",
-  "kling-v2.1-master-text-to-video",
-  "kling-v3-turbo-text-to-video"
-]

Changed2 schema fields changedv0.2.0Sep 30, 2026

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"
+]

changedInput schema / properties / model / enum

Previous value: -[
-  "kling-ai-avatar-pro",
-  "kling-ai-avatar-standard",
-  "kling-ai-avatar-v1-pro",
-  "kling-v1-avatar-standard",
-  "kling-v2.5-turbo-image-to-video-pro",
-  "kling-v2.5-turbo-text-to-video-pro",
-  "kling-o1",
-  "kling-v2.1-master-image-to-video",
-  "kling-v2.1-pro",
-  "kling-v2.1-standard",
-  "kling-v2.6",
-  "kling-v3-omni",
-  "kling-v3-turbo-image-to-video",
-  "kling-3.0",
-  "kling-v2.1-master-text-to-video",
-  "kling-v3-turbo-text-to-video"
-]New value: +[
+  "kling-ai-avatar-pro",
+  "kling-ai-avatar-standard",
+  "kling-ai-avatar-v1-pro",
+  "kling-v1-avatar-standard",
+  "kling-v3-omni-edit",
+  "kling-v3-omni-reference",
+  "kling-v2.5-turbo-image-to-video-pro",
+  "kling-v2.5-turbo-text-to-video-pro",
+  "kling-o1",
+  "kling-v2.1-master-image-to-video",
+  "kling-v2.1-pro",
+  "kling-v2.1-standard",
+  "kling-v2.6",
+  "kling-v3-omni",
+  "kling-v3-turbo-image-to-video",
+  "kling-3.0",
+  "kling-v2.1-master-text-to-video",
+  "kling-v3-turbo-text-to-video"
+]

Changed2 schema fields changedv0.1.13Jul 29, 2026

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"
+]

changedInput schema / properties / model / enum

Previous value: -[
-  "kling-ai-avatar-pro",
-  "kling-ai-avatar-standard",
-  "kling-ai-avatar-v1-pro",
-  "kling-v1-avatar-standard",
-  "kling-v2.1-master-image-to-video",
-  "kling-v2.1-pro",
-  "kling-v2.1-standard",
-  "kling-v2.5-turbo-image-to-video-pro",
-  "kling-v3-turbo-image-to-video",
-  "kling-3.0",
-  "kling-v2.1-master-text-to-video",
-  "kling-v2.5-turbo-text-to-video-pro",
-  "kling-v3-turbo-text-to-video"
-]New value: +[
+  "kling-ai-avatar-pro",
+  "kling-ai-avatar-standard",
+  "kling-ai-avatar-v1-pro",
+  "kling-v1-avatar-standard",
+  "kling-v2.5-turbo-image-to-video-pro",
+  "kling-v2.5-turbo-text-to-video-pro",
+  "kling-o1",
+  "kling-v2.1-master-image-to-video",
+  "kling-v2.1-pro",
+  "kling-v2.1-standard",
+  "kling-v2.6",
+  "kling-v3-omni",
+  "kling-v3-turbo-image-to-video",
+  "kling-3.0",
+  "kling-v2.1-master-text-to-video",
+  "kling-v3-turbo-text-to-video"
+]

Changed1 schema field changedv0.1.9Jul 22, 2026

changedInput schema / properties / model / enum

Previous value: -[
-  "kling-ai-avatar-pro",
-  "kling-ai-avatar-standard",
-  "kling-ai-avatar-v1-pro",
-  "kling-v1-avatar-standard",
-  "kling-v2.1-master-image-to-video",
-  "kling-v2.1-pro",
-  "kling-v2.1-standard",
-  "kling-v2.5-turbo-image-to-video-pro",
-  "kling-3.0",
-  "kling-v2.1-master-text-to-video",
-  "kling-v2.5-turbo-text-to-video-pro"
-]New value: +[
+  "kling-ai-avatar-pro",
+  "kling-ai-avatar-standard",
+  "kling-ai-avatar-v1-pro",
+  "kling-v1-avatar-standard",
+  "kling-v2.1-master-image-to-video",
+  "kling-v2.1-pro",
+  "kling-v2.1-standard",
+  "kling-v2.5-turbo-image-to-video-pro",
+  "kling-v3-turbo-image-to-video",
+  "kling-3.0",
+  "kling-v2.1-master-text-to-video",
+  "kling-v2.5-turbo-text-to-video-pro",
+  "kling-v3-turbo-text-to-video"
+]

First observedv0.1.1Jun 23, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. 'Look up' implies a safe read, but the description does not state whether pricing is real-time or cached, whether auth is required, or what the lookup returns (per-call, per-second, currency), which matters greatly for a pricing tool with no output schema.

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 waste; the resource and scope appear immediately. Nothing extraneous is included.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description should explain what the pricing result looks like and any auth or rate constraints, but it says nothing about the return value. For a tool whose entire purpose is retrieving pricing data, this leaves a significant gap.

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 schema already documents both params including the action enum and the default behavior, making the baseline 3 appropriate. The phrase 'kling model line' hints that the model param is constrained to kling slugs, but no semantic detail is added beyond the schema.

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?

The description states a specific verb and resource ('Look up RunAPI pricing') and scopes it to the 'kling model line', which is clear enough for an agent to understand the operation. It does not differentiate from siblings, but no sibling tool overlaps with pricing lookup, so the risk of confusion is low.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing explains when an agent should call this versus acting on pricing info, nor any prerequisite such as needing a model slug first. With both params optional, the description does not indicate any situation in which the tool is or isn't appropriate.

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

Deploy Server

check_pricing

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools