Skip to main content
Glama

Ludo AI Game Assets

by ai.ludo
OverviewDiscussionsAdmin

createVideoFromReferences

Generate a video from 1-5 reference images and a text prompt (references-to-video). Unlike createVideo, which animates a single source image, this composes a new scene that borrows characters, objects, and style from the reference images. Each image can be a URL or base64. Griffin (default, 480p) and Griffin HD (720p) generate a soundtrack; note the per-second rate here is higher than createVideo's for the same model. The job result is the video URL and its actual duration in seconds. Choose the output shape with aspect_ratio ("default" lets the model decide). The chosen model and duration must be compatible (incompatible combinations return HTTP 400). Credits are held when the job is accepted; the final charge is max(rate × produced seconds, the model's minimum charge), never more than for the duration you requested, and the difference (or everything, if the job fails or is cancelled) is refunded. Pass an optional request_id to tag the result so you can locate it later via listGenerations (type video). Related tools: createVideo for image-to-video, editVideo to modify a generated video. Async generation job: returns {id, status} - poll getApiJob (job and credit contract: see the server instructions).

Credits: credits/s × seconds, per model: Griffin 2.5/s (shortest duration 5s, so 12.5 credits minimum), Griffin HD 4/s (shortest duration 5s, so 20 credits minimum), Eagle 1.5/s [LEGACY], Eagle with Audio 2/s [LEGACY]; [LEGACY] models are scheduled for removal - do not use them for new work; see this endpoint's full pricing table in the API docs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestBodyYesPayload for generating a video from 1-5 reference images and a text prompt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / requestBody / properties / model / description
      Previous value: -"Model to use. Available models:\n- \"griffin\" (Griffin): 2.5 credits/s\n- \"griffin-hd\" (Griffin HD): 4 credits/s\n- \"eagle\" (Eagle): 1.5 credits/s · LEGACY - scheduled for removal, do not use for new work\n- \"eagle-audio\" (Eagle with Audio): 2 credits/s · LEGACY - scheduled for removal, do not use for new work\nModels marked LEGACY still work for existing integrations but will be removed; pick a current model for anything new. Default: \"eagle\"."New value: +"Model to use. Available models:\n- \"griffin\" (Griffin): 2.5 credits/s, shortest duration 5s, so 12.5 credits minimum · Fast cinematic videos in any style, with audio, 480p\n- \"griffin-hd\" (Griffin HD): 4 credits/s, shortest duration 5s, so 20 credits minimum · Same as Griffin, but in 720p\n- \"eagle\" (Eagle): 1.5 credits/s · LEGACY - scheduled for removal, do not use for new work\n- \"eagle-audio\" (Eagle with Audio): 2 credits/s · LEGACY - scheduled for removal, do not use for new work\nModels marked LEGACY still work for existing integrations but will be removed; pick a current model for anything new. Default: \"griffin\"."
    • changedInput schema / properties / requestBody / properties / model / example
      Previous value: -"eagle"New value: +"griffin"
    • changedInput schema / properties / requestBody / properties / request_id / description
      Previous value: -"Optional client-provided identifier, unique per request. Re-sending the same request_id returns the existing job instead of generating again. Also usable with the results endpoint."New value: +"Optional client-provided identifier, unique per request. Re-sending the same request_id returns the existing job instead of generating again. Also usable as the request_id filter of listGenerations."
  2. Changed1 schema field changed
    • changedInput schema / properties / requestBody / properties / model / description
      Previous value: -"Model to use. Available models:\n- \"griffin\" (Griffin): 2.5 credits/s\n- \"griffin-hd\" (Griffin HD): 4 credits/s\n- \"eagle\" (Eagle): 1.5 credits/s\n- \"eagle-audio\" (Eagle with Audio): 2 credits/s Default: \"eagle\"."New value: +"Model to use. Available models:\n- \"griffin\" (Griffin): 2.5 credits/s\n- \"griffin-hd\" (Griffin HD): 4 credits/s\n- \"eagle\" (Eagle): 1.5 credits/s · LEGACY - scheduled for removal, do not use for new work\n- \"eagle-audio\" (Eagle with Audio): 2 credits/s · LEGACY - scheduled for removal, do not use for new work\nModels marked LEGACY still work for existing integrations but will be removed; pick a current model for anything new. Default: \"eagle\"."
  3. Changed3 schema fields changed
    • changedInput schema / properties / requestBody / properties / duration / description
      Previous value: -"Duration in seconds. Available values depend on the model:\n- eagle: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15\n- eagle-audio: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15 Default: 5."New value: +"Duration in seconds. Available values depend on the model:\n- griffin: 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15\n- griffin-hd: 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15\n- eagle: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15\n- eagle-audio: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15 Default: 5."
    • changedInput schema / properties / requestBody / properties / model / description
      Previous value: -"Model to use. Available models:\n- \"eagle\" (Eagle): Visual Quality: 8/10 · Motion Stability: 5/10 · 1.5 credits/s\n- \"eagle-audio\" (Eagle with Audio): Visual Quality: 8/10 · Motion Stability: 5/10 · 2 credits/s Default: \"eagle\"."New value: +"Model to use. Available models:\n- \"griffin\" (Griffin): 2.5 credits/s\n- \"griffin-hd\" (Griffin HD): 4 credits/s\n- \"eagle\" (Eagle): 1.5 credits/s\n- \"eagle-audio\" (Eagle with Audio): 2 credits/s Default: \"eagle\"."
    • changedInput schema / properties / requestBody / properties / model / enum
      Previous value: -[
-  "eagle",
-  "eagle-audio"
-]New value: +[
+  "griffin",
+  "griffin-hd",
+  "eagle",
+  "eagle-audio"
+]
  4. Changed3 schema fields changed
    • changedInput schema / properties / requestBody / properties / duration / description
      Previous value: -"Duration in seconds. Available values depend on the model:\n- eagle: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15\n- eagle-audio: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15\n- forge-pixel: 1, 1.5, 2, 2.5, 3, 3.5, 4 Default: 5."New value: +"Duration in seconds. Available values depend on the model:\n- eagle: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15\n- eagle-audio: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15 Default: 5."
    • changedInput schema / properties / requestBody / properties / model / description
      Previous value: -"Model to use. Available models:\n- \"eagle\" (Eagle): Visual Quality: 8/10 · Motion Stability: 5/10 · 1.5 credits/s\n- \"eagle-audio\" (Eagle with Audio): Visual Quality: 8/10 · Motion Stability: 5/10 · 2 credits/s\n- \"forge-pixel\" (Forge Pixel): 2 credits/s, min 4 Default: \"eagle\"."New value: +"Model to use. Available models:\n- \"eagle\" (Eagle): Visual Quality: 8/10 · Motion Stability: 5/10 · 1.5 credits/s\n- \"eagle-audio\" (Eagle with Audio): Visual Quality: 8/10 · Motion Stability: 5/10 · 2 credits/s Default: \"eagle\"."
    • changedInput schema / properties / requestBody / properties / model / enum
      Previous value: -[
-  "eagle",
-  "eagle-audio",
-  "forge-pixel"
-]New value: +[
+  "eagle",
+  "eagle-audio"
+]
  5. Changed6 schema fields changed
    • removedInput schema / properties / requestBody / properties / aspect_ratio / default
      Removed value: -"default"
    • changedInput schema / properties / requestBody / properties / aspect_ratio / description
      Previous value: -"Output aspect ratio. \"default\" lets the model choose."New value: +"Output aspect ratio. \"default\" lets the model choose. Default: \"default\"."
    • removedInput schema / properties / requestBody / properties / duration / default
      Removed value: -5
    • changedInput schema / properties / requestBody / properties / duration / description
      Previous value: -"Duration in seconds. Available values depend on the model:\n- eagle: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15\n- eagle-audio: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15\n- forge-pixel: 1, 1.5, 2, 2.5, 3, 3.5, 4"New value: +"Duration in seconds. Available values depend on the model:\n- eagle: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15\n- eagle-audio: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15\n- forge-pixel: 1, 1.5, 2, 2.5, 3, 3.5, 4 Default: 5."
    • removedInput schema / properties / requestBody / properties / model / default
      Removed value: -"eagle"
    • changedInput schema / properties / requestBody / properties / model / description
      Previous value: -"Model to use. Available models:\n- \"eagle\" (Eagle): Visual Quality: 8/10 · Motion Stability: 5/10 · 1.5 credits/s\n- \"eagle-audio\" (Eagle with Audio): Visual Quality: 8/10 · Motion Stability: 5/10 · 2 credits/s\n- \"forge-pixel\" (Forge Pixel): 2 credits/s, min 4"New value: +"Model to use. Available models:\n- \"eagle\" (Eagle): Visual Quality: 8/10 · Motion Stability: 5/10 · 1.5 credits/s\n- \"eagle-audio\" (Eagle with Audio): Visual Quality: 8/10 · Motion Stability: 5/10 · 2 credits/s\n- \"forge-pixel\" (Forge Pixel): 2 credits/s, min 4 Default: \"eagle\"."
  6. Changed1 schema field changed
    • changedInput schema / properties / requestBody / properties / request_id / description
      Previous value: -"Optional client-provided identifier for this request. Use this to retrieve results later via the results endpoint."New value: +"Optional client-provided identifier, unique per request. Re-sending the same request_id returns the existing job instead of generating again. Also usable with the results endpoint."
  7. Changed3 schema fields changed
    • changedInput schema / properties / requestBody / properties / duration / description
      Previous value: -"Duration in seconds. Available values depend on the model:\n- eagle: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15\n- eagle-audio: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15"New value: +"Duration in seconds. Available values depend on the model:\n- eagle: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15\n- eagle-audio: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15\n- forge-pixel: 1, 1.5, 2, 2.5, 3, 3.5, 4"
    • changedInput schema / properties / requestBody / properties / model / description
      Previous value: -"Model to use. Available models:\n- \"eagle\" (Eagle): Visual Quality: 8/10 · Motion Stability: 5/10 · 1.5 credits/s\n- \"eagle-audio\" (Eagle with Audio): Visual Quality: 8/10 · Motion Stability: 5/10 · 2 credits/s"New value: +"Model to use. Available models:\n- \"eagle\" (Eagle): Visual Quality: 8/10 · Motion Stability: 5/10 · 1.5 credits/s\n- \"eagle-audio\" (Eagle with Audio): Visual Quality: 8/10 · Motion Stability: 5/10 · 2 credits/s\n- \"forge-pixel\" (Forge Pixel): 2 credits/s, min 4"
    • changedInput schema / properties / requestBody / properties / model / enum
      Previous value: -[
-  "eagle",
-  "eagle-audio"
-]New value: +[
+  "eagle",
+  "eagle-audio",
+  "forge-pixel"
+]
  8. Added

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden, and it delivers: it discloses async behavior ('returns {id, status} - poll getApiJob'), the credit hold/refund policy ('Credits are held when the job is accepted; the final charge is max(...), never more than... and the difference... is refunded'), model/duration incompatibility errors ('incompatible combinations return HTTP 400'), the soundtrack generation for Griffin models, and legacy deprecation ('do not use them for new work'). These are meaningful behavioral traits that structured annotations would normally provide, so the description compensates well.

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 description is thorough and front-loaded with the main purpose and contrast, which is good, but it is verbose and contains redundancy with the schema. The pricing block at the end largely repeats the model enum descriptions in the schema, and phrases like 'Each image can be a URL or base64' are already in the images parameter description. Every sentence adds some value, but several could be trimmed without loss, making it less concise than ideal for a complex tool.

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?

The description covers the core workflow (async job, polling, result format), credit handling, compatibility constraints, legacy deprecation, related tools, and return details. There is no output schema, so explaining 'The job result is the video URL and its actual duration in seconds' is essential and included. It does not enumerate all possible error conditions beyond HTTP 400, but it gives enough for an agent to use the tool correctly. Given the tool's complexity and absence of annotations, this is a high but not perfect level of completeness.

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 description coverage is 100%, so the baseline is 3, but the description adds value beyond the schema. It explains the credit implications of model selection ('per-second rate here is higher than createVideo's for the same model') and details the pricing per model, which helps agents pick a cost-effective option. It also clarifies how request_id can be used to locate results via listGenerations, which is not fully spelled out in the schema. While the schema already documents each parameter's meaning, the description enriches the model and request_id semantics enough to justify a 4.

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?

The description opens with a specific verb and resource: 'Generate a video from 1-5 reference images and a text prompt (references-to-video).' It goes beyond a simple restatement by explicitly differentiating from the sibling tool: 'Unlike createVideo, which animates a single source image, this composes a new scene that borrows characters, objects, and style from the reference images.' An agent can immediately distinguish this tool from createVideo without opening either schema.

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?

The description names the alternatives and the selection criterion: 'Related tools: `createVideo` for image-to-video, `editVideo` to modify a generated video.' It also clarifies the boundary with 'Unlike createVideo, which animates a single source image...' and describes the async workflow, making it clear when to use this tool and how to follow up via getApiJob. This is explicit when/when-not guidance, not just implied.

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

All Ludo AI Game Assets toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources