Skip to main content
Glama

timeline_create

Creates a new timeline and makes it current, with optional custom resolution, frame rate, start timecode, settings, and ordered clips for immediate editing.

Instructions

Create a new timeline and make it current. Optional custom resolution (e.g. 1080x1920 for vertical), fps ('25', '29.97' — prefer setting the PROJECT fps with project_create before any timeline exists; changing a timeline's fps by script is fragile in Resolve), start timecode, other timeline settings, and initial clips: media refs (whole clips) or segments {"media":..., "in":sec, "out":sec} appended in order.

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

Input Schema

NameRequiredDescriptionDefault
binNo
fpsNo
nameYes
clipsNo
widthNo
heightNo
settingsNo
start_timecodeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses the key side effect that the new timeline becomes current, warns that changing a timeline fps by script is fragile in Resolve, and says initial clips are appended in order. It does not cover failure cases, duplicate-name behavior, permissions, atomicity, or what is returned.

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?

The key action is front-loaded in the first clause, and the rest of the description is dense but mostly earns its place by covering parameter formats and a behavioral caveat. The long fps parenthetical is useful but makes the sentence heavier than ideal.

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 an 8-parameter create tool with no annotations, no output schema, and 0% schema description coverage, the description covers most of the complex parameter semantics. It leaves gaps around the 'bin' parameter, valid 'settings' keys, media-ref syntax details, and failure or return behavior, so it is adequate but not complete.

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 compensate. It explains width and height through the custom-resolution example, gives fps string examples and a fragile-change warning, names start timecode and settings, and documents the clips format for whole media refs versus in/out segments appended in order. The 'bin' parameter is not explained at all, which keeps it from 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?

The description gives a specific verb and resource: 'Create a new timeline and make it current.' That is enough to distinguish it from timeline_open, timeline_import, and timeline_manage, but it does not explicitly differentiate it from other create tools such as compound_create or multicam_create.

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?

It implies usage by describing creation and an optional initial clips list, and it gives a conditional recommendation for fps: prefer setting the project fps with project_create before any timeline exists. It does not state when to choose timeline_create over sibling creation or import tools, nor does it list exclusions or prerequisites beyond the fps note.

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