Skip to main content
Glama

Generate a video clip

generate_video

Generate a video clip from a prompt with a hosted model and put it on the timeline. The clip takes its place on the timeline at start straight away, and the finished video fills it when the run ends. Quality standard (default, Kling: 5 or 10 s, 16:9 / 9:16 / 1:1, silent) or best (Veo 3.1: 4 / 6 / 8 s, 16:9 / 9:16, optional audio, costs more). model: "wan-3.0" takes any length from 2 to 30 s in one generation, 16:9 / 9:16 / 1:1 at 720p unless resolution says otherwise, with free synchronised audio; it cuts between listed scenes itself and keeps the same people across them, so a story of several scenes that fits in 30 s and starts from nothing is one Wan 3.0 run (name each recurring person once with their look, then the scenes in order) rather than a clip per scene. A 30 s take waits about twelve minutes. model: "gemini-omni-flash" is 3-8 s at 720p (1080p when resolution asks for it), 16:9 / 9:16, always with native audio, and holds a four-scene story in 8 s. image turns a project image into the first frame and routes on its own to Hailuo 02 (standard) or Kling 3 Pro (best), which animate a still faithfully; describe only the motion. ref lists stills and videos the model works from rather than starts on (a product, a place, a move to copy): name them @Image1, @Image2… and @Video1… in the prompt in the order given. model: "seedance-2.5" takes up to 9 stills and 3 videos (30 s of video in all; clip.mp4#2-8 sends seconds 2 to 8, and each second sent bills like a generated one at a lower rate); Seedance refuses any ref showing a real-looking person, so it takes no cast; MiniMax H3 and Wan 3.0 take stills only. People who must come back in another video, or in a scene you will redo on its own: write them as @Name in the prompt and describe the action, not the person. The first time a name is used, pass character: ["Name: who they are, hair, wardrobe"]; the job draws a reference sheet, keeps it in the project (the timeline header lists the cast; the sheet stills stay out of media listings) and later shots just say @Name. Cast everyone who recurs, kids included, or they change every shot. Cast shots at standard run 5-15 s on MiniMax H3 straight from the sheet stills; at best, 3-10 s on Kling 3 Pro from a drawn first frame for one person, or 2-30 s on Wan 3.0 from the sheet for two. A shot with more than one @Name goes to best on its own unless quality or model is given. motion only applies to the first-frame recipe. Open a cast shot medium or closer on one action so the face is large enough to keep; a wide, fast, many-body frame comes back with the face deformed. Returns at once with the generation id; generation_status with wait: true waits up to about half a minute at a time and fills the pending clip when the run ends. Costs credits; the error says what to fix.

Input Schema

NameRequiredDescriptionDefault
refNoReference stills and videos (media ids or names; a video takes #from-to), @Image1/@Video1 in order
nameNoClip name; default: the prompt, shortened
seedNo
waitNotrue waits for the result in this call (a long run hands back a job); default: return at once
audioNoGenerate sound (best tier only)
imageNoFirst frame: media id or file name
modelNoExact model id; overrides quality
startNoTimeline seconds; default: after the track’s last clip
trackNoTrack name or id; default: first video track or a new "Generated" one
aspectNoDefault: the project’s, or the closest the model renders
motionNoWith a cast member: the action alone for the video model; the prompt then shapes the first frame
promptYesWhat the clip should show; be concrete about subject, motion and camera
projectYesProject id or exact name
qualityNo
characterNo"Name: description" for each @Name in the prompt the project does not know yet
resolutionNoWhere the model offers a choice; 720p when unset. Each size bills its own rate
negativePromptNo
durationSecondsNoClip length; each model offers a fixed set

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well past the annotations: it discloses credit cost, ~12 minute wait for a 30 s take, that it returns at once with a generation id, that a pending clip is placed on the timeline immediately, that character reference sheets persist in the project and are hidden from media listings, and that errors explain what to fix. The annotations only supply the generic non-read-only, non-destructive profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, but the body is a dense ~400-word block with no lists or headings despite covering a dozen distinct routing rules, making it hard to scan. Most sentences do carry information, though a few pack several independent rules into one run-on clause.

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?

For an 18-parameter generation tool with no output schema, the description covers the essentials: what is created, where it lands, what comes back (generation id), how to wait for completion, cost, and per-model constraints. An agent could call this correctly without further documentation.

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 83%, so the schema already carries much of the load, yet the description adds real meaning for `model`, `quality`, `image`, `ref`, `character`, `motion`, `resolution`, and `durationSeconds` (per-model length limits, ref naming syntax like `@Image1`, `clip.mp4#2-8` ranges, cast description format). It is silent on `seed` and `negativePrompt`, and only lightly touches `start`/`track` defaults that the schema already covers.

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 concrete verb and resource ('Generate a video clip from a prompt') and immediately names the side effect ('put it on the timeline'), which separates it from generate_image, generate_music, and the search/read siblings. The model routing detail further pins down what this tool uniquely does.

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 routes between alternatives: standard vs best tiers, when a multi-scene story is one Wan 3.0 run rather than a clip per scene, when `image` (first-frame) applies versus `ref` (reference material), and which models reject cast refs. It also names the follow-up tool ('generation_status with `wait: true`') and gives a composition rule for cast shots.

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