Skip to main content
Glama

Claude Imagine

by com.claudeimagine
OverviewDiscussionsAdmin

Generate Video

generate_video
Destructive

Generate an AI video with H3 Max Turbo (default: renders in seconds, 5-15 s), Grok Imagine, Seedance, Veo, or Kling. Every account gets its first H3 Max Turbo clip at 5 s / 480p free; after that it costs credits like any other preset. Users can name a model family naturally: H3, Hailuo or MiniMax map to H3 Max Turbo, Veo to Veo 3.1 Fast, Kling to Kling 2.5 Turbo, Grok to Grok Imagine, Seedance to Seedance 2.0 Mini, and Seedance Pro to Seedance 1.5 Pro. Never omit model when the user named one. Call list_models or quote_generation first when the user wants to review models and costs before spending credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNoVideo model or friendly name. Shortcuts: h3, hailuo or minimax -> h3-max-turbo; grok -> grok-imagine; seedance or seedance-mini -> seedance-2.0-mini; seedance-pro -> seedance-1.5-pro; veo -> veo-3.1-fast; kling -> kling-2.5-turbo. Defaults to h3-max-turbo only when the user did not name a model.
promptYesVideo description
durationNoSeconds: H3 Max Turbo 5-15, Grok 6-30, Seedance 1.5 Pro 4-12, Seedance 2.0 Mini 4-15, Veo 3.1 Fast 4/6/8, Kling 5/10. Defaults to the selected model preset.
image_urlNoOptional public image URL to animate
resolutionNoQuality: H3 Max Turbo supports 480p/768p; Grok and Seedance 1.5 support 480p/720p/1080p; Seedance 2.0 Mini supports 480p/720p; Veo 3.1 Fast currently uses 720p; Kling uses fixed Pro quality.
max_creditsNoBudget cap in credits, when the person stated one. If the exact cost of this call is above it, nothing is started and the reply lists what fits.
aspect_ratioNoVideo aspect ratio, default 16:9. Veo supports 16:9 or 9:16; Kling and H3 Max Turbo image-to-video follow the source image instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / max_credits
      Added value: +{
+  "description": "Budget cap in credits, when the person stated one. If the exact cost of this call is above it, nothing is started and the reply lists what fits.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
  2. Changed6 schema fields changed
    • changedInput schema / properties / aspect_ratio / description
      Previous value: -"Video aspect ratio, default 16:9. Veo supports 16:9 or 9:16; Kling image-to-video follows the source image instead."New value: +"Video aspect ratio, default 16:9. Veo supports 16:9 or 9:16; Kling and H3 Max Turbo image-to-video follow the source image instead."
    • changedInput schema / properties / duration / description
      Previous value: -"Seconds: Grok 6-30, Seedance 1.5 Pro 4-12, Seedance 2.0 Mini 4-15, Veo 3.1 Fast 4/6/8, Kling 5/10. Defaults to the selected model preset."New value: +"Seconds: H3 Max Turbo 5-15, Grok 6-30, Seedance 1.5 Pro 4-12, Seedance 2.0 Mini 4-15, Veo 3.1 Fast 4/6/8, Kling 5/10. Defaults to the selected model preset."
    • changedInput schema / properties / model / description
      Previous value: -"Video model or friendly name. Shortcuts: grok -> grok-imagine; seedance or seedance-mini -> seedance-2.0-mini; seedance-pro -> seedance-1.5-pro; veo -> veo-3.1-fast; kling -> kling-2.5-turbo. Defaults to grok-imagine only when the user did not name a model."New value: +"Video model or friendly name. Shortcuts: h3, hailuo or minimax -> h3-max-turbo; grok -> grok-imagine; seedance or seedance-mini -> seedance-2.0-mini; seedance-pro -> seedance-1.5-pro; veo -> veo-3.1-fast; kling -> kling-2.5-turbo. Defaults to h3-max-turbo only when the user did not name a model."
    • changedInput schema / properties / model / enum
      Previous value: -[
-  "grok-imagine",
-  "seedance-1.5-pro",
-  "seedance-2.0-mini",
-  "veo-3.1-fast",
-  "kling-2.5-turbo",
-  "grok",
-  "seedance",
-  "seedance-mini",
-  "seedance-pro",
-  "veo",
-  "kling"
-]New value: +[
+  "h3-max-turbo",
+  "grok-imagine",
+  "seedance-1.5-pro",
+  "seedance-2.0-mini",
+  "veo-3.1-fast",
+  "kling-2.5-turbo",
+  "h3",
+  "hailuo",
+  "minimax",
+  "grok",
+  "seedance",
+  "seedance-mini",
+  "seedance-pro",
+  "veo",
+  "kling"
+]
    • changedInput schema / properties / resolution / description
      Previous value: -"Quality: Grok and Seedance 1.5 support 480p/720p/1080p; Seedance 2.0 Mini supports 480p/720p; Veo 3.1 Fast currently uses 720p; Kling uses fixed Pro quality."New value: +"Quality: H3 Max Turbo supports 480p/768p; Grok and Seedance 1.5 support 480p/720p/1080p; Seedance 2.0 Mini supports 480p/720p; Veo 3.1 Fast currently uses 720p; Kling uses fixed Pro quality."
    • changedInput schema / properties / resolution / enum
      Previous value: -[
-  "480p",
-  "720p",
-  "1080p"
-]New value: +[
+  "480p",
+  "720p",
+  "768p",
+  "1080p"
+]
  3. Added

TDQS

A5/5.0
Behavior5/5

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

Discloses that the first H3 Max Turbo clip is free, subsequent usage costs credits, and the max_credits parameter caps spending with a defined behavior (nothing started, reply lists what fits). This goes beyond the annotations by detailing cost-related behavior and budget handling.

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?

Though relatively long, every sentence provides necessary detail: model options, aliases, cost policy, defaults, and when to defer to sibling tools. The structure is logical and front-loaded with the core action, without redundant or unrelated content.

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

Completeness5/5

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

Given the sibling tools (check_generation, quote_generation, list_models, get_credits), the description covers the full context: what to do before generating, how to set budget, and what model to choose. The absence of an output schema is acceptable since the tool likely starts an async job and returns a generation ID, which is implicitly covered by the sibling check_generation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema descriptions cover all 7 parameters (100% coverage), and the description text adds valuable aliases and default rules (e.g., 'h3' -> h3-max-turbo, default only when user did not name a model). This fully clarifies parameter meaning and allowed values.

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 tool generates AI videos, specifies the models available, and distinguishes it from siblings like generate_image and edit_image. The verb 'Generate' and resource 'AI video' are explicit, and the model list differentiates it from other tools.

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?

Explicitly instructs when to call list_models or quote_generation first, namely when the user wants to review models and costs before spending credits. Also clarifies when to omit the model parameter, providing unambiguous usage guidance.

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

All Claude Imagine toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources