Skip to main content
Glama

get_timeline

Lists clips, tracks, and markers in the active editor timeline so you can inspect and plan precise edits.

Instructions

List the clips, tracks and markers of the active sequence/timeline in the current editor.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; "List" reasonably conveys a read-only, non-destructive operation with no side effects. However, it does not disclose failure behavior when no sequence is active, the depth or size of the returned structure, or whether the result reflects unsaved edits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the verb, the returned entities, and the scope all appear immediately. Nothing could be removed without losing information.

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 zero-parameter read tool with no output schema, the description does name the three returned entity types (clips, tracks, markers), which is the key missing structured information. It stops short of describing result shape or ordering, but that is a minor gap at this complexity.

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?

The tool takes zero parameters, so the baseline is 4 and the description has nothing parameter-related to compensate for. It correctly implies no input is needed to retrieve the active timeline contents.

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 ("List") and enumerates the resources returned (clips, tracks, markers), scoped to the active sequence/timeline in the current editor. An agent can distinguish it from siblings like editor_status or show_plan by the explicit resource list, though it never names an alternative to contrast against.

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 rather than stated: "active sequence/timeline in the current editor" signals this reads the currently loaded edit context, not an arbitrary project. There is no explicit when-to-use, when-not-to-use, or named alternative such as editor_status or show_plan.

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