VideoGen

Remix project

remix_project

Destructive

Use for AI video editing of an existing VideoGen project: apply caption, transition, or camera-motion edits, or animate its still images. The original project is edited in place unless saveAsNewProject is true; use that flag when the user wants a separate version. CONVERT_IMAGES_TO_VIDEOS generates clips from every still and uses substantial team credits. ZOOM adds camera motion at lower cost. Use only actions in the input schema; this is not arbitrary timeline editing. Poll list_project_remix_actions until edits finish, then export_project for a fresh MP4.

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": {
      "projectId": "<projectId>",
      "edits": "<edits>"
    },
    "name": "remix_project"
  }
}

Input Schema

Name	Required	Description
`edits`	Yes	Curated edits to apply in order. CONVERT_IMAGES_TO_VIDEOS generates AI video clips from every still and is expensive. Use ZOOM for cheap Ken Burns camera motion.
`projectId`	Yes	Editable project to remix. Use projectId from a workflow result, list_projects, or get_project.
`saveAsNewProject`	No	When true, duplicate the project and apply edits to the copy. When omitted, edit the original project in place.

Output Schema

Name	Required	Description
`projectId`	Yes	Edited project id (or the duplicate when saveAsNewProject).
`projectUrl`	Yes	Deep link to the project in the VideoGen editor.
`remixActionIds`	Yes	Remix action ids, one per requested action in order.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 16, 2026

changedInput schema / properties / projectId / description

Previous value: -"Project id to edit."New value: +"Editable project to remix. Use projectId from a workflow result, list_projects, or get_project."

changedInput schema / properties / saveAsNewProject / description

Previous value: -"Apply edits to a copy of the project."New value: +"When true, duplicate the project and apply edits to the copy. When omitted, edit the original project in place."

First observedOct 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the destructiveHint=true annotation, it explains exactly what is mutated (the original project, in place) and the escape hatch (saveAsNewProject duplicates first). It also discloses cost/credit asymmetry between actions and the asynchronous completion pattern, which annotations cannot convey.

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 purpose and mutation semantics, then cost, then the polling/export follow-up. Every sentence carries information, though the single dense paragraph packs several distinct concerns (mutation, cost, workflow, restriction) that would read more cleanly as short clauses.

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 destructive, credit-consuming async mutation, the description covers mutation scope, the copy-vs-in-place decision, cost tradeoffs, action restriction, and the post-call polling/export sequence. An output schema exists, so return values need not be described.

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 coverage is 100%, so the baseline is 3; the description earns above that by explaining the intent of saveAsNewProject (separate version vs in-place) and the cost tradeoff between CONVERT_IMAGES_TO_VIDEOS and ZOOM. It stops short of adding anything about projectId sourcing beyond what the schema already says.

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 ("AI video editing of an existing VideoGen project") and enumerates the concrete edit categories (caption, transition, camera-motion, animate stills). It also draws a hard boundary ("this is not arbitrary timeline editing"), which separates it from generation siblings like generate_video_clip or video_to_video.

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?

Gives explicit routing: use saveAsNewProject when a separate version is wanted, prefer ZOOM over CONVERT_IMAGES_TO_VIDEOS for zoom/pan, then poll list_project_remix_actions and finally call export_project. It names the downstream and upstream siblings by name, so the agent knows the surrounding workflow without inference.

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

All VideoGen tools Inspect

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.