Skip to main content
Glama

import_into_timeline

Import an AAF file into an existing DaVinci Resolve timeline, optionally specifying import options and source clip bin paths.

Instructions

Import an AAF into an existing timeline (see get_api_type('AAFImportOptions'); sourceClipsFolders may be bin paths).

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": "import_into_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
optionsNo
timelineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a useful pointer to get_api_type('AAFImportOptions') and notes sourceClipsFolders may be bin paths, but says nothing about overwrite/merge behavior on the target timeline or permission needs.

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?

A single compact sentence with the core action front-loaded and parenthetical detail after it. Efficient, though the parentheticals are dense enough to be cryptic on first read.

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 three-parameter mutation tool with no output schema and zero schema description coverage, the definition leaves the required path semantics and the timeline selector unexplained. The get_api_type pointer is genuinely helpful but not enough to make the tool invocable without inspecting external API docs.

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 coverage is 0%, so the description carries the burden and only partly meets it: it points at the AAFImportOptions type for the 'options' parameter and clarifies that sourceClipsFolders values may be bin paths. The required 'path' parameter and the 'timeline' parameter (which accepts a name string or integer id) get no explanation at all.

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: importing an AAF into an *existing* timeline, which implicitly separates it from import_timeline (creating a new one). An agent can mostly tell what it does, though the sibling differentiation is implied rather than stated.

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 'into an existing timeline' hints that this is for adding to a timeline that already exists rather than creating one, but it never says when to prefer it over import_timeline or append_to_timeline. Usage must be inferred.

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

Deploy Server

Other Tools