Skip to main content
Glama

append_to_timeline

Append clips to a DaVinci Resolve timeline and place sub-ranges precisely using source frames, track, record frame, and media type.

Instructions

Append clips to a timeline (current by default). Each entry is a clip reference or {"clip", "start", "end" (source frames), "track" (1-based), "record_frame" (timeline frame), "media": "video"|"audio"} to place sub-ranges precisely.

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": {
      "clips": "<clips>"
    },
    "name": "append_to_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipsYes
timelineNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 the meaningful default of operating on the current timeline, but says nothing about what happens on failure, whether partial appends are atomic, whether the append point is end-of-timeline, or what the response contains. Adequate, not rich, beyond annotations.

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 action and default, then the entry grammar. The inline pseudo-JSON is information-dense and mostly earns its space, though the shorthand is terse enough to require interpretation on first read.

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

Completeness4/5

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

For a two-parameter, non-destructive append tool with no output schema and no annotations detail, the definition covers both parameters, the default timeline, and the sub-range placement semantics. Remaining gaps (clip-reference syntax, return value, error behavior) are minor at this complexity level.

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

Parameters4/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 carry parameter meaning, and it does: it explains that clips entries may be bare clip references or objects with clip, start/end in source frames, 1-based track, record_frame, and a video/audio media flag, plus that timeline defaults to the current one. It stops short of saying what a 'clip reference' is (ID, path, name) or what form the timeline string/integer takes, keeping it below a 5.

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?

Names a specific verb and resource (append clips to a timeline) and states the default target (current timeline), so the agent knows exactly what the call achieves. It does not explicitly contrast with nearby siblings such as import_into_timeline or create_timeline, which would have earned a 5.

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?

Usage is implied by 'current by default' and by the precise sub-range form, which suggests this is the tool for placing clips at exact source/record frames. There is no explicit when-to-use versus when-not guidance and no named alternative for bulk import or timeline creation.

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