Skip to main content
Glama

timeline_export

Export a DaVinci Resolve timeline to AAF, EDL, FCPXML, OTIO, CSV, or ALE files. Specify the path and format to hand off edits, audio, or metadata to other tools.

Instructions

Export the timeline to a file. format: aaf | drt | edl | edl_cdl | edl_sdl | edl_missing | fcp7xml | fcpxml (1.10) | fcpxml_1_9 | fcpxml_1_8 | otio | csv | tab | ale | ale_cdl | hdr10_a | hdr10_b | dolby_vision.

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": {
      "path": "<path>"
    },
    "name": "timeline_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
formatNofcpxml
timeline_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioural burden, and it discloses almost nothing beyond the act of exporting. It never says whether an existing file at `path` is overwritten, what permissions or an open project it requires, whether the operation blocks, or what happens on an unsupported format. Only the format taxonomy is offered as extra information.

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?

Two sentences, front-loaded with the core action before the format list. The long pipe-delimited format enumeration is verbose but earns its place because the schema declares no enum, making the description the only source of valid values.

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?

For a three-parameter mutation that writes a file to disk with no annotations and no output schema, the definition is only partially complete. It covers the format vocabulary well but leaves the destination-path behaviour and the meaning of the optional timeline_name unspecified, which are the two things an agent most needs to call it safely.

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 0%, and the description compensates for the most important gap by enumerating the valid `format` values (aaf, drt, edl variants, fcpxml versions, otio, csv, tab, ale variants, hdr10, dolby_vision), which the schema itself does not constrain. It says nothing about `path` (overwrite semantics, extension handling) or `timeline_name` (what happens when null — presumably the active timeline, but that is left to inference).

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?

The description states a specific verb and resource: 'Export the timeline to a file.' That is unambiguous about what the tool produces. It does not, however, distinguish itself from siblings such as quick_export, project_export, or render_timeline, so an agent gets no help choosing among the export family from this text alone.

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?

There is no statement of when to use this tool versus quick_export, project_export, render_timeline, or metadata_export. The implicit reading is 'use this to export a timeline,' but no exclusions, prerequisites, or alternative-routing advice are given.

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