Skip to main content
Glama

timeline_import

Import AAF, EDL, XML, FCPXML, DRT, ADL, or OTIO files as a new timeline, or merge an AAF into the current timeline.

Instructions

Import a timeline from AAF/EDL/XML/FCPXML/DRT/ADL/OTIO as a new timeline (or, with into_current=true and an AAF, into the current timeline).

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_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
pathYes
into_currentNo
source_clips_pathNo
import_source_clipsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It does disclose the key mutation semantics (creates a new timeline vs. writes into the current one) and the format/mode restriction on into_current, but says nothing about what happens on failure, whether existing current-timeline content is altered, media handling, or return value.

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 tight sentence with the verb and scope front-loaded and the conditional mode caveat placed second. Nothing is wasted and no filler precedes the actionable content.

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

Completeness2/5

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

For a five-parameter mutation tool with no annotations and no output schema, the description is too thin: three parameters are undocumented and there is no information about results or side effects on the current timeline. An agent could pick the wrong flags for source-clip import without ever knowing they exist.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate and it largely does not: name, source_clips_path, and import_source_clips are never mentioned, and path/into_current are only partially explained (formats and the AAF-only constraint). Two of five parameters get indirect treatment, leaving most semantics to be guessed from bare titles and defaults.

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 (import) and resource (timeline) and enumerates the accepted interchange formats (AAF/EDL/XML/FCPXML/DRT/ADL/OTIO), which makes it clearly distinct from generic siblings like project_import or media_import. It does not explicitly say how it differs from timeline_create, but the format list does most of the differentiating work.

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 parenthetical gives a concrete selection rule: use into_current=true only with an AAF to land in the current timeline, otherwise a new timeline is created. That is real when-to-use guidance. It stops short of naming alternatives (e.g., timeline_create) or stating exclusions such as prerequisites for the source file.

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