Skip to main content
Glama

timeline_get

Retrieves the current timeline's tracks, clips, and timecodes, optionally filtered by track or time window. Use it to inspect edit structure before trimming, grading, or rendering.

Instructions

The edit of the current timeline: every track (name, enabled, locked) with its clips (ref, id, name, start/end seconds + frames, source in/out, media id). Filter by tracks (["V1","A1"]) and a time window. detail=true adds properties, speed, fades, linked clips, comps, markers per clip.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "timeline_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
startNo
detailNo
tracksNo
markersNo
timeline_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the exact shape of the returned data (tracks with name/enabled/locked, clips with timing and source in/out), which is genuinely useful behavior information. It never states read-only nature, cost, or volume limits for large timelines, and does not clarify what happens when a time window matches nothing.

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 return payload is front-loaded, then filters, then the detail flag — a logical read order with no filler sentences. Minor awkwardness in 'The edit of the current timeline' costs a little clarity but nothing is wasted.

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?

With six optional parameters, 0% schema coverage, and no output schema, the description does substantial work by documenting the return structure. However it leaves `timeline_name` and `markers` unexplained, and the mention of `timeline_name` conflicts with the 'current timeline' framing, leaving an agent unsure how to target a non-active timeline.

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 coverage is 0%, so the description must compensate; it explains `tracks` with a concrete example (["V1","A1"]), the time-window intent behind start/end, and what `detail` unlocks. Three of six parameters — `markers`, `timeline_name`, and the exact start/end units/format — are left undefined, and `timeline_name` in particular is unexplained given the description says 'current timeline'.

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 names a specific resource (the current timeline's tracks and clips) and enumerates the returned fields, so an agent knows exactly what data it gets. It does not distinguish itself from siblings such as clip_info or clips_select_info, which likely overlap on clip-level data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus alternatives like clip_info or timeline_open, nor any precondition or exclusion. The filtering hints ('Filter by `tracks`', 'detail=true adds properties') are parameter mechanics rather than routing guidance.

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