Skip to main content
Glama

create_timeline

Creates an empty timeline or builds one from clips in a specified or default bin, including optional source frame ranges for sub-clip edits.

Instructions

Create a timeline (empty, or from clips) in bin (default current bin). Each clip is a clip reference or {"clip", "start", "end", "record_frame"} with source frames for a sub-range.

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

Input Schema

NameRequiredDescriptionDefault
binNo
nameYes
clipsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds the meaningful behavioral detail that the timeline may contain no clips and that a bin may be omitted in favor of the current bin. It does not say whether the new timeline becomes the current timeline, what is returned, or whether write permissions on the target bin are required.

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 tight sentences, front-loaded with the core action before the payload-format detail. Every clause carries information; no filler or hedging.

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 three-parameter creation tool with only hint annotations and no output schema, the definition covers the ambiguous part well — the clip payload format — and states the bin defaulting rule. It stops short of describing what the tool returns (timeline id or object) or whether the created timeline becomes current, which an agent likely needs for chaining.

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 0% and the clips array is typed as bare `items: {}`, but the description compensates substantially by specifying that each clip is either a clip reference or a dict with "clip", "start", "end", "record_frame" and what source frames mean. However, the required `name` parameter is never explained (though its meaning is obvious from context), and the interaction between bin=null and the current bin is only restated from the schema default. As baseline when schema is empty but description partly compensates, below the 4 it could reach with full parameter coverage.

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 ("Create a timeline") and immediately distinguishes two modes: empty, or populated from clips. That is more than a restatement of the name, though it never names the sibling tools it competes with (append_to_timeline, import_timeline, create_compound_clip).

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 only implied: the description tells the agent creation can be empty or populated from clips, and that the bin defaults to the current bin. There is no explicit guidance on when to call create_timeline versus append_to_timeline or import_timeline, nor any stated prerequisite (e.g. whether a project must be open).

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