Skip to main content
Glama

Image to cinematic video (Video AI)

luw_generate_video

Animate a design image into a short cinematic video with selectable camera motions; optionally add an end frame to create before-and-after transitions.

Instructions

Luw.ai Video AI (Motion): animate a design image into a short cinematic video — fly-throughs, dolly moves, drone shots, reveals. Camera motions: A Forward Dolly, Flythrough Cinematic, Return to Empty Room, Lighting and Color Details, Drone flying to center, Dramatic Zoom Out, Reverse Zoom In, Slow Pull Back, Reveal Zoom, Ground to Sky Tilt, Side Tracking Zoom, Aerial Descent. Pass end_image to make the video end on that frame, e.g. the original photo as image and its redesign as end_image for a before → after transition. Takes a few minutes — expect a processing_url to collect with luw_get_result. Costs 10 credits (aria) or 20 (symphony), with or without end_image.

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": {
      "image": "<image>"
    },
    "name": "luw_generate_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageYesStart frame (a render or photo) (public https:// link or data: URI; the local npx server also accepts a file path).
engineNoLuw.ai model: aria (default) or symphony (Symphony-3).
promptNoWhat should happen in the video.
end_imageNoOptional end frame the video moves to; use the start frame's aspect ratio (public https:// link or data: URI; the local npx server also accepts a file path).
camera_motionNoOne of the camera motions listed above, e.g. "Flythrough Cinematic".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.18
    • changedInput schema / properties / end_image / description
      Previous value: -"Optional end frame the video moves to; use the start frame's aspect ratio (https:// URL, local file path, or data: URI)."New value: +"Optional end frame the video moves to; use the start frame's aspect ratio (public https:// link or data: URI; the local npx server also accepts a file path)."
    • removedInput schema / properties / enhance_prompt
      Removed value: -{
      -  "description": "Let Luw.ai's prompt enhancer expand a short prompt.",
      -  "type": "boolean"
      -}
    • changedInput schema / properties / image / description
      Previous value: -"Start frame (a render or photo) (https:// URL, local file path, or data: URI)."New value: +"Start frame (a render or photo) (public https:// link or data: URI; the local npx server also accepts a file path)."
    • removedInput schema / properties / seed
      Removed value: -{
      -  "description": "Fix for reproducible results.",
      -  "maximum": 9007199254740991,
      -  "minimum": 0,
      -  "type": "integer"
      -}
  2. Changed1 schema field changedv0.3.2
    • addedInput schema / properties / end_image
      Added value: +{
      +  "description": "Optional end frame the video moves to; use the start frame's aspect ratio (https:// URL, local file path, or data: URI).",
      +  "minLength": 1,
      +  "type": "string"
      +}
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say it is a non-read-only, open-world, non-idempotent call. The description adds what actually matters operationally: a multi-minute runtime, that the call returns a processing_url to poll, and exact credit costs per engine — none of which is in the schema or annotations.

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 core action and the end_image trick, then cost/latency last. The long camera-motion enumeration is bulky but functionally necessary since the schema defers to it; still, it dominates the prose.

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 a five-parameter, no-output-schema generation tool, it covers what the agent needs: what it produces, how results are retrieved (processing_url + luw_get_result), how long, and what it costs.

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 coverage is 100%, so per-parameter documentation is already handled; the baseline is 3. The description does add value by enumerating the valid camera_motion values (the schema only says 'one of the camera motions listed above') and by tying engine choice to cost, but prompt/image semantics are left entirely to the schema.

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 ('animate a design image into a short cinematic video') and enumerates the motion types, which distinguishes it clearly from sibling generation/edit tools like luw_generate_image or luw_image_to_3d.

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?

Explains the end_image use case concretely (original photo as image, redesign as end_image for a before → after transition) and routes the agent to luw_get_result for collection. It does not state when to prefer a sibling tool instead, so it stops short of full when/when-not guidance.

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