Skip to main content
Glama

Sequencer

by media.sequencer
OverviewDiscussionsAdmin

update_edit

Update an existing edit (project). Supports partial updates — only provided fields are changed.

Input Schema

NameRequiredDescriptionDefault
styleNoOne short sentence describing only the visual aesthetic shared by every shot (e.g., "cinematic noir, dramatic lighting, subtle film grain"). Do not include characters, locations, props, actions, or shot-specific details.
titleNoNew title for the edit
editIdYesThe edit ID to update
videoModelNoDefault model ID for shot video generations
aspectRatioNoDefault aspect ratio for new media
speechModelNoDefault model ID for speech generation. Defaults to Cartesia Sonic 3.5 (cartesia-sonic-3-5) for new edits.
transitionsNoComplete replacement list of timeline transition boundary objects. Use fromShotId/toShotId for robust adjacency-based transitions.
workspaceIdYesThe workspace ID
styleAssetIdsNoLegacy array of explicitly supplied style-reference asset IDs. Routine projects use the edit.style text and should leave this unset.
shotImageModelNoDefault model ID for shot still/image generations
sceneImageModelNoDefault model ID for scene/location image generations
defaultImageModelNoDefault model ID for new image generations. Also updates shotImageModel, sceneImageModel, and characterImageModel unless those are provided separately. Defaults to google-nano-banana-2-1 for new edits.
defaultVideoModelNoDefault model ID for new video generations. Also updates videoModel unless videoModel is provided separately. Defaults to google-gemini-omni-1-1 for new edits.
characterImageModelNoDefault model ID for character image generations

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / defaultImageModel / description
      Previous value: -"Default model ID for new image generations. Also updates shotImageModel, sceneImageModel, and characterImageModel unless those are provided separately. Defaults to google-gemini-3-image for new edits."New value: +"Default model ID for new image generations. Also updates shotImageModel, sceneImageModel, and characterImageModel unless those are provided separately. Defaults to google-nano-banana-2-1 for new edits."
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the valuable PATCH-style semantics ('only provided fields are changed'), but omits permissions, reversibility, and any destructive/overwrite caveats for a mutation tool.

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?

Two short sentences with zero filler, and the core action plus its most important behavioral trait are front-loaded. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 14 well-documented params, high schema coverage, and no output schema, the description covers the essentials of a partial-update tool. However, for an unannotated mutation it lacks permission/side-effect disclosure and any routing to alternative update tools.

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 the schema already documents all 14 parameters thoroughly (including cascading behavior of defaultImageModel/defaultVideoModel and replacement semantics of transitions). The description adds only the partial-update note and no further per-parameter meaning, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Update') and resource ('an existing edit (project)'), which cleanly separates it from create_edit, get_edit, and get_edit_full. It does not explicitly name or differentiate from near siblings like update_scene or update_shot, so it falls short of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It notes that partial updates are supported, but gives no when-to-use context, no prerequisites (workspaceId + editId both required), and no guidance on when to prefer this over sibling mutation tools such as update_scene. Usage is left entirely to inference.

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

All Sequencer 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