Skip to main content
Glama

generate_video

Create video clips from text prompts or a local reference image, then save the output locally with its file path, cost, and remaining credits.

Instructions

Generate a video clip and save it locally. Returns the file path, cost and remaining credits.

prompt: the shot - subject, action, camera move, light. model: video model id (see list_models(kind="video")), default veo-3.1-fast. aspect: "16:9", "9:16" (some models also "1:1" etc.). option: duration such as "4s", "6s", "8s"; must be one the model offers. image_path: optional local image for image-to-video (first frame / reference). Video takes 1-5 minutes; the call waits up to 10 minutes.

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": "generate_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoveo-3.1-fast
aspectNo16:9
optionNo8s
promptYes
image_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries full weight and delivers key behavior: the operation is a blocking call that waits up to 10 minutes, clips take 1-5 minutes, and the response includes cost and remaining credits. It omits what happens on timeout/failure and whether a job_status fallback exists, which keeps it short of a 5.

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?

Purpose and return values are front-loaded, then parameters in a terse one-line-per-param list, then a latency note. Nearly every line earns its place; the mixed list/prose structure is slightly informal but not wasteful.

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

Completeness4/5

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

An output schema exists, so return values need only be summarized, and the description still names them. Latency, blocking behavior, defaults, and cost implications are covered; only error/timeout handling and file persistence details are absent for a long-running generative tool.

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?

Schema description coverage is 0%, yet the description documents all five parameters: prompt content expectations, model with default and discovery path, aspect values, duration format and model-dependent constraint, and image_path as an optional local first-frame/reference. This fully compensates for the bare 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?

States a concrete verb and resource ('Generate a video clip') plus the side effect of saving locally and returning file path, cost, and remaining credits. The 'video' resource implicitly separates it from generate_audio and generate_image siblings, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

Gives actionable routing guidance for values: model ids come from list_models(kind="video"), duration must be one the chosen model offers, and image_path is only for image-to-video. It does not state when to prefer a still-image or audio sibling instead, but usage context is otherwise clear.

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