gflow_generate_video
Generate a video using Google Flow's Veo model. Modes: t2v (text-to-video), i2v (image-to-video), r2v (reference-to-video). Aspects: 9:16, 16:9.
Instructions
Generate a video using Google Flow's Veo model. Modes: t2v (text-to-video), i2v (image-to-video), r2v (reference-to-video). Aspects: 9:16, 16:9. Optional model (veo_lite/veo_fast/veo_quality/omni_flash/omni_1_2_flash), duration (seconds; omni_1_2_flash takes 3-15, at most 10 with an end_frame), and count select the Veo model, clip length, and batch size (CLI parity). The prompt supports @CharacterName mentions to tag saved project characters by name (resolves to referenceEntities; on flow.google.com a video @Name is not supported yet, exit 29 before submit, so pass reference_entities plus reference_entity_names to r2v). Reference a SAVED character via @Name; pass one-off ingredient images via reference_images. See docs/REFERENCE_STRATEGIES.md. Optional ui_mode ('classic'/'auto') verifies the classic editor pre-submit and aborts before spending credits if unreachable; 'agentic' is not supported for video. out_file, if given, must resolve inside the configured output directory. Returns the local file path to the generated video.
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": {
"prompt": "<prompt>"
},
"name": "gflow_generate_video"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | t2v | |
| wait | No | true (default): run the generation inside this call and return the finished result. The call stays open for the whole generation, minutes for a video, which can outlast an MCP client's tool timeout; raise that timeout, or use false. false: return {status: 'pending', task_id} at once and run the job in the background of this server process. With the SEP-2663 Tasks extension, poll tasks/get by task_id: while it runs the status is working; once done it is completed and its result field holds the same reply wait=true would (files, project id, seed). A failed generation is also completed, with result.isError true, so check isError. tasks/cancel aborts the job locally; tasks/get then reads cancelled. A job not yet submitted to Flow stops before submitting and nothing is charged; once a gflow worker has submitted it, Flow cannot cancel it, so it may still be charged (statusMessage says which). gflow cancel <id> is the CLI twin. The job runs only while this server runs: if the client closes the server, it is cancelled. | |
| count | No | ||
| model | No | ||
| tools | No | Prompt tools applied before generation. Each item is {"name": <slug>, "options": {...}}, e.g. [{"name": "creative-director"}]. gflow_list_tools lists the valid names. | |
| aspect | No | 9:16 | |
| prompt | Yes | ||
| profile | No | default | |
| project | No | ||
| ui_mode | No | ||
| duration | No | ||
| out_file | No | Optional file to write, inside the configured output dir: a relative path is taken relative to it; an escape or a directory is refused. | |
| end_frame | No | ||
| resolution | No | ||
| project_name | No | ||
| initial_frame | No | ||
| reference_images | No | ||
| reference_entities | No | Saved character entity ids to attach. On flow.google.com each id needs its display name at the same position in reference_entity_names, or the call fails before submit; gflow_character_list returns both. Character references need mode r2v there. | |
| reference_entity_names | No | Display name of each reference_entities id, same order. Required on flow.google.com, where an id without its name fails before submit. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||