Skip to main content
Glama

AI Video Generator - Abracadabrax

Prepare AI Video

prepare_ai_video

Prepare a text-to-video clip with Abracadabrax from a scene description: visual style, landscape (YouTube), vertical (TikTok, Reels, Shorts) or square format, length in seconds and video model (Kling, Seedance, Sora, Veo). Returns the settings and the credits required; nothing is generated and no credits are spent. No sign-in is needed to prepare. Text only: do not use it for uploaded, attached or reference images or videos (editing, background removal, upscaling, image-to-video); for those, point the user to the Abracadabrax workspace.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "scene": "<scene>"
    },
    "name": "prepare_ai_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
sceneYesWhat happens in the clip: subject, action, setting, camera movement, lighting.
styleNoVisual style, e.g. cinematic, anime, 3D animation, documentary, claymation.
formatNolandscape 16:9 (default), vertical 9:16 or square 1:1 (square only on Kling and Seedance).
durationNoLength in seconds; must be one the model supports (Kling 5 or 10, Seedance 5-12, Sora 4/8/12, Veo 4/6/8).
model_idNoOptional video model id: kling-3-pro (default), kling-3-standard, seedance-1-5-pro, seedance-1-lite, sora-2, veo-3-1-fast, veo-3-1.

Output Schema

NameRequiredDescriptionDefault
jobNo
stateYes
balanceNo
messageYes
projectYes
dashboard_urlYes
credits_requiredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial behavioral context beyond the annotations: nothing is generated, no credits are spent, and no sign-in is required, which tells the agent this is a safe dry-run-style preparation call. Annotations only supply readOnly=false / destructive=false / idempotent=false; the description supplies the cost-free, auth-free, non-generating profile that actually governs agent behaviour.

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?

Front-loaded with the action and two dense sentences that each carry real content (outputs, side-effect limits, auth, exclusions). The parenthetical enumerations of platforms and models are somewhat heavy, but no sentence is disposable.

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?

With an output schema present, the description need not explain return values, yet it still notes that settings and required credits come back. Combined with the exclusions, auth note and format coverage, an agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema lacks: platform mappings for formats ('landscape (YouTube), vertical (TikTok, Reels, Shorts)') and the set of selectable models. It does not add duration-validity or default guidance beyond what the enum descriptions already carry.

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?

States a specific verb+resource ('prepare a text-to-video clip') and enumerates the concrete dimensions it configures (style, format, duration, model). It explicitly distinguishes this tool from image/video editing, background removal, upscaling and image-to-video work, so an agent can separate it from siblings like generate_media without opening a schema.

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?

Gives explicit when-to-use (text-only scene descriptions) and when-not-to-use ('do not use it for uploaded, attached or reference images or videos'), plus a fallback route ('point the user to the Abracadabrax workspace'). The alternative for non-text inputs is named rather than left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources