Skip to main content
Glama

Generate video

generate_video

Submit a video generation request through Rainbrand’s public API. Use a supported video model returned by list_models and follow its published input schema from get_model. Returns the generation ID and its current status. Retrieve and inspect outputs with get_generation.

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": {
      "brand_session_id": "<brand_session_id>",
      "model": "<model>",
      "input": "<input>"
    },
    "name": "generate_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesArguments for the selected model, using the field names and reference formats published by get_model.
modelYesModel to run. Choose an ID from list_models whose output type matches the generation tool being called.
brief_idNoCompleted Brief to use for this generation. Rainbrand adds its guidance before your prompt and its visual assets after any references you provide.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.
idempotency_keyNoRetry key for recovering the original generation after an uncertain response. Reuse it with identical arguments. Without a key, repeating the request starts another generation.
brand_session_idYesBrand session ID from list_brands for the brand this generation belongs to.

Output Schema

NameRequiredDescriptionDefault
idYesGeneration ID. Pass it as id to get_generation.
statusYesCurrent generation status.
message_for_assistantNoContext, explanations, or actionable guidance for the calling assistant. Hosts may display it, but it is not copy that must be shown to the user verbatim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare a non-read-only, open-world, non-destructive operation, so the description only needs to add context — and it does, by stating the call returns a generation ID plus current status, which signals asynchronous submission rather than a completed render. It does not mention credit consumption or rate limits despite a check_credits sibling existing, which keeps it from 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.

Conciseness5/5

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

Three short sentences, front-loaded with the action, then prerequisites, then the follow-up tool. No filler, no restatement of the title, and each sentence carries distinct information.

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?

For a complex tool with a nested free-form `input` object and an output schema, the description covers selection (model), shaping (get_model schema), and retrieval (get_generation) — the three things an agent must know. The only gap is timing semantics: whether the call blocks or returns immediately is inferable from "current status" but not stated outright.

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

Parameters3/5

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

Schema description coverage is 100%, so all six parameters — including the polymorphic `input` object and the idempotency key — are already documented in the schema itself. The description's note about following get_model's published input schema largely restates the `input` property's own description, adding little new meaning, so the baseline of 3 applies.

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 and resource — "Submit a video generation request" — and the video modality distinguishes it from generate_image and generate_audio without needing their schemas opened. It also scopes the operation to Rainbrand's public API and names the dependent lookups (list_models, get_model).

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 a clear prerequisite chain: pick a supported model from list_models and follow its input schema from get_model, then retrieve results with get_generation. That routes the agent forward and backward well. It stops short of explicit when-not-to-use guidance (e.g., when to prefer generate_image, or checking credits first), so it is not a full 5.

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