Skip to main content
Glama

Ludo AI Game Assets

by ai.ludo
OverviewDiscussionsAdmin

editVideo

Edit a previously generated video with a text prompt and optional reference images (video-to-video); runs on griffin-hd (720p, with soundtrack) and the output keeps the source video's duration unless you pass one. Pass the video url you received from createVideo, createVideoFromReferences, or an earlier edit - it must be a video you generated within the last 7 days; arbitrary external videos are not accepted. Optionally add up to 5 reference images (URL or base64) to guide the edit. The job result is the new video URL and its actual duration in seconds. 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 to generate the source clip, createVideoFromReferences for reference-driven generation. Async generation job: returns {id, status} - poll getApiJob (job and credit contract: see the server instructions).

Credits: credits/s × seconds, per model: Griffin HD 2/s (shortest duration 5s, so 10 credits minimum), Eagle 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 editing a previously generated video with a text prompt and optional reference images.

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-hd\" (Griffin HD): 2 credits/s\n- \"eagle\" (Eagle): 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-hd\" (Griffin HD): 2 credits/s, shortest duration 5s, so 10 credits minimum · Same as Griffin, but in 720p\n- \"eagle\" (Eagle): 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-hd\"."
    • changedInput schema / properties / requestBody / properties / model / example
      Previous value: -"eagle"New value: +"griffin-hd"
    • 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-hd\" (Griffin HD): 2 credits/s\n- \"eagle\" (Eagle): 2 credits/s Default: \"eagle\"."New value: +"Model to use. Available models:\n- \"griffin-hd\" (Griffin HD): 2 credits/s\n- \"eagle\" (Eagle): 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"New value: +"Duration in seconds. Available values depend on the model:\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"
    • 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 · 2 credits/s Default: \"eagle\"."New value: +"Model to use. Available models:\n- \"griffin-hd\" (Griffin HD): 2 credits/s\n- \"eagle\" (Eagle): 2 credits/s Default: \"eagle\"."
    • changedInput schema / properties / requestBody / properties / model / enum
      Previous value: -[
-  "eagle"
-]New value: +[
+  "griffin-hd",
+  "eagle"
+]
  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- 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"
    • 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 · 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 · 2 credits/s Default: \"eagle\"."
    • changedInput schema / properties / requestBody / properties / model / enum
      Previous value: -[
-  "eagle",
-  "forge-pixel"
-]New value: +[
+  "eagle"
+]
  5. Changed2 schema fields changed
    • 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 · 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 · 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"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- 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 · 2 credits/s"New value: +"Model to use. Available models:\n- \"eagle\" (Eagle): 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"
-]New value: +[
+  "eagle",
+  "forge-pixel"
+]
  8. Added

TDQS

A4.5/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden, and it delivers richly: async job semantics (returns {id, status}, poll getApiJob), the credit hold/refund formula, duration behavior (keeps source duration unless overridden), model legacy warnings, and the output contract (new video URL + actual duration). This goes well beyond a minimal disclosure.

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 purpose, then input constraints, billing, async behavior, and related tools in a logical order. It is long, but nearly every sentence earns its place given the billing and async complexity; only mild redundancy with the schema's model descriptions keeps it from a 5.

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 request body, async execution, no output schema, and a credit system, the description covers the essential operational facts: how to source the video, how to poll, what the result contains, and the pricing contract. Minor gaps (error handling, job duration expectations) are deferred to the server instructions, which is a reasonable boundary.

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% and each parameter already has rich per-property descriptions (model enum with credits, video 7-day constraint, images maxItems, request_id idempotency). The description adds modest extra meaning, e.g. that duration defaults to the source video's length and the credit charge formula, but the schema already carries most of the semantic load, so baseline 3 is appropriate.

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 + resource + manner: 'Edit a previously generated video with a text prompt and optional reference images (video-to-video)'. It clearly distinguishes from siblings by naming createVideo and createVideoFromReferences as source-generating tools and by the video-to-video framing, which separates it from editImage.

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?

Provides explicit when-to-use guidance: input must be a video generated within the last 7 days via createVideo, createVideoFromReferences, or a prior edit, and arbitrary external videos are rejected. It names related tools with their roles ('createVideo to generate the source clip, createVideoFromReferences for reference-driven generation'), giving the agent a clear routing decision.

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