Skip to main content
Glama

list_timeline

Read-only

Lists an active sequence's tracks, clips with IDs and timing, transitions, and markers so you can inspect timeline structure before editing.

Instructions

The active sequence: tracks, clips (ids, timeline start/end and source in/out in seconds), transitions and markers. raw=true returns FilmCraft's full sequence.inspect JSON.

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

Input Schema

NameRequiredDescriptionDefault
rawNo
projectNoPath to the .fcproj project file; omit to edit the FilmCraft app connected with connect_app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds real value by disclosing the returned structure, including units (seconds) for clip timing, and by flagging that raw=true switches to FilmCraft's native sequence.inspect JSON — a materially different payload. It does not mention size limits, truncation, or behavior when no project is connected.

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 with no filler, and the returned-content inventory comes first so the agent learns what it gets before the raw-mode caveat. The first sentence is a bare noun-phrase fragment, which is dense but slightly telegraphic; otherwise the structure is efficient.

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?

With no output schema, the description must carry the return-value burden, and it does so by enumerating fields and their units. For a zero-required-parameter read tool this is close to complete; only the no-project/no-connection case and any payload size caveat are unaddressed.

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 coverage is 50%: `project` is documented in the schema, but `raw` carries no schema description. The description fills exactly that gap by explaining raw=true yields FilmCraft's full sequence.inspect JSON, which tells the agent this is a verbose/native-format escape hatch rather than a filter. That is meaningful semantic content beyond the structured fields.

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 enumerates exactly what the tool surfaces — the active sequence's tracks, clips with ids and start/end plus source in/out in seconds, transitions and markers — which is specific, concrete content, not a restatement of the name. It stops short of naming a verb or differentiating itself from near-neighbours such as inspect_project or export_timeline, so an agent must infer that this is a read of the current sequence rather than a project-level or file-level dump.

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 when-to-use guidance and no exclusions; the description never says to prefer this over inspect_project or export_timeline. The only usage-shaped statement is the raw=true note, which is a parameter hint rather than a routing rule. An agent must already know the sibling set to choose correctly.

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