Skip to main content
Glama

export_timeline

Export the active sequence as an interchange timeline in XML, AAF, FCPXML, EDL, or OTIO to move edits into Premiere, Resolve, or another editing app.

Instructions

Export the active sequence as an interchange timeline for other editors (Premiere: xml / aaf; Resolve: xml / fcpxml / edl / otio).

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": {
      "output": "<output>"
    },
    "name": "export_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoxml
outputYes
projectNoPath to the .fcproj project file; omit to edit the FilmCraft app connected with connect_app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false, so the write nature is signaled but little else. The description adds that the output is an interchange file for other NLEs, yet it never says the tool writes a file to the 'output' path, whether an existing file is overwritten, or which formats preserve what (e.g., aaf/omf for audio).

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?

A single front-loaded sentence with the action first and the format mapping as supporting detail; no filler or redundant restatement of the tool name.

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 write tool with no output schema, the description covers the conceptual purpose but not the operational contract: no return-value expectation, no overwrite behavior, and no explanation of how 'project' differs from the app connected via connect_app despite the description's reference to the 'active sequence'. Adequate but with clear gaps.

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 33%: only 'project' is documented in the schema, while the required 'output' parameter has no explanation anywhere — file path vs. directory is unresolved. The description partially compensates by explaining what the format enum values are for, but it leaves the required parameter and the default format untouched.

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 and resource ('Export the active sequence as an interchange timeline'), which separates it from media-producing siblings like render and export_frames. The per-NLE format mapping adds useful specificity, but the description omits 'omf' from the schema enum and its fcpxml-under-Resolve placement is loose, so it is not fully precise.

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

Usage Guidelines3/5

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

The phrase 'for other editors' implies the handoff/round-trip use case versus render or export_frames, but the choice is left to inference. There is no explicit when-to-use or when-not-to-use statement and no mention of prerequisites such as connect_app or an open project.

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