Skip to main content
Glama

Timeline (write)

timeline_write
Destructive

Modify DaVinci Resolve timeline state by adding markers, tracks, and clips; renaming, importing/exporting, and setting timecodes or track states. Changes are read back to verify they took effect.

Instructions

Change timeline state; may overwrite current values. Every change is read back from Resolve (receipt.verified=false means it did not take). op.action (params; * = required):

  • add_marker(frame*, color, name, note, duration, custom_data): Add a marker at a frame offset of a timeline.

  • add_markers(markers*): Add several markers in one call; frames already occupied are skipped.

  • add_track(type*, sub_type): Add a video, audio or subtitle track (audio accepts a sub type).

  • append_clips(clips*): Append Media Pool clips to a timeline (end frames exclusive, record offsets relative).

  • auto_align_clips(items*, sync_using, use_track): Align timeline items by timecode or waveform (Resolve 21.1+).

  • clear_mark_in_out(type): Clear mark in/out.

  • convert_to_stereo(): Convert the timeline to stereoscopic 3D.

  • create_compound_clip(items*, name, start_timecode): Create a compound clip from timeline items.

  • create_fusion_clip(items*): Create a Fusion clip from timeline items.

  • create_timeline(name*): Create an empty timeline in the current Media Pool folder.

  • create_timeline_from_clips(name*, clips*): Create a timeline from Media Pool clips (optional source in/out per clip).

  • duplicate_timeline(name*): Duplicate a timeline under a new name; the current timeline is left unchanged.

  • export_timeline(path*, format*, subtype): Export a timeline (EDL, XML, AAF, DRT, OTIO, ...) to a file.

  • import_into_timeline(path*, insert_additional_tracks, insert_with_offset, source_clips_path, link_to_source_camera_files, use_sizing_info): Import items from an AAF file into an existing timeline.

  • import_timeline(path*, timeline_name, import_source_clips, source_clips_path, interlace_processing): Create a timeline from an EDL/XML/AAF/DRT/OTIO file.

  • insert_generated(kind*, name): Insert a generator, title, OFX or Fusion generator/title/comp at the playhead.

  • rename_timeline(name*): Rename a timeline (the new name must be unique).

  • rename_track(track*, name*): Rename a track.

  • set_clips_linked(items*, linked*): Link or unlink timeline items.

  • set_current_timecode(timecode*): Move the playhead to a timecode (from the Edit page when Resolve is on Media).

  • set_current_timeline(): Make a timeline the current one.

  • set_mark_in_out(mark_in*, mark_out*, type): Set mark in/out (frames relative to timeline start).

  • set_output_blanking(top, bottom, left, right): Set the timeline output blanking in pixels (Resolve 21.1+).

  • set_settings(settings*): Set timeline settings (verified key by key; some keys are silently refused).

  • set_start_timecode(timecode*): Set the timeline start timecode.

  • set_track_enabled(track*, enabled*): Enable or disable a track.

  • set_track_locked(track*, locked*): Lock or unlock a track (a locked V1 makes Insert* calls fail).

  • update_marker_custom_data(frame*, custom_data*): Replace the custom data of the marker at a frame offset. Shortcuts (prefer them for whole tasks):

  • workflow_write.build_vertical_reel: Build a vertical timeline from clips, add subtitles and optionally render it. One call instead of create_timeline, create_timeline_from_clips, set_settings.

  • workflow_write.conform_from_edl: Import media + EDL as a timeline, fix offline events via Start TC, report linkage. One call instead of import_timeline, set_start_timecode. Calls known in advance (a sequence, the same change on several items): ONE batch_run.

Input Schema

NameRequiredDescriptionDefault
opYes{action, ...params}. Parameters per action: see the description or this server's describe_action tool.
dry_runNotrue: return the planned effect, change nothing.
snapshotNotrue: back up the timeline/project first; omitted: server policy.

Output Schema

NameRequiredDescriptionDefault
jobNo
planNo
statusYes
receiptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.4
    • addedInput schema / properties / dry_run / description
      Added value: +"true: return the planned effect, change nothing."
    • addedInput schema / properties / snapshot / description
      Added value: +"true: back up the timeline/project first; omitted: server policy."
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructive/non-idempotent, but the description adds real value beyond them: changes are read back from Resolve and receipt.verified=false means the change did not take, frames already occupied are skipped, some settings keys are silently refused, a locked V1 makes Insert* calls fail, and several actions are gated on Resolve 21.1+. That is exactly the failure-mode disclosure annotations cannot carry.

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?

The most important caveat (overwrite risk plus the read-back verification contract) is front-loaded in the first sentence, the action reference is a dense one-line-per-action table with no filler, and routing advice is grouped at the end. Length is justified by 28 actions that the schema does not document.

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 28-action dispatch tool with a nested generic schema, this covers action inventory, per-action params, required markers, version gates, known failure modes, and preferred shortcut wrappers. An output schema exists and receipt semantics are mentioned, so return-value explanation is not owed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema's op object is generic ({action, ...params}), so the per-action parameter table is doing the real documentation work — listing each action's params with '*' marking required ones and noting constraints like 'the new name must be unique' and 'end frames exclusive, record offsets relative'. The 100% schema coverage refers only to the three top-level keys, so this description-level compensation is essential and well executed.

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?

Opens with a specific verb+resource+scope: 'Change timeline state; may overwrite current values.' Then enumerates all 28 legal actions, so an agent knows exactly what domain this covers and can distinguish it from timeline_read/timeline_delete by name and content.

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?

The 'Shortcuts (prefer them for whole tasks)' block explicitly routes the agent to workflow_write.build_vertical_reel and workflow_write.conform_from_edl, and 'ONE batch_run' covers multi-change sequences — genuine alternative-routing. What's missing is explicit counter-routing against the read/delete siblings or conditions where the tool should not be used at all.

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