Skip to main content
Glama

timelines

List all project sequences with name, ID, duration, fps, and tracks, and identify the currently active one.

Instructions

List all timelines in the project (name, id, duration, fps, tracks) and which one is current.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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; it does establish that this is a non-mutating enumeration and it discloses the shape of each entry, including the current-timeline flag. It says nothing about ordering, pagination on large projects, or required project context, which are the remaining behavioral unknowns for a listing tool.

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 sentence with a parenthetical field list — front-loaded, zero filler, and the most useful detail (current timeline) is placed at the end for emphasis. Nothing here could be cut 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 simple zero-parameter read tool with no output schema, the description is nearly sufficient: it enumerates returned fields and flags the current timeline. What is missing is only tangential context such as ordering or behavior on an empty project, which is minor.

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 there is no parameter semantics to explain and the baseline score applies. The description adds value by describing the output fields instead, filling a gap left by the absent output schema.

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?

Names a specific verb and resource ("List all timelines in the project") and enumerates the fields the listing exposes (name, id, duration, fps, tracks) plus the current-timeline marker. No sibling tool in the supplied catalog covers timelines, so there is nothing to confuse it with, though no explicit exclusion is stated.

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 by the scoping phrase "in the project" and the mention of "which one is current". It does not state when an agent should call this versus other discovery tools such as api_search or clip_info, nor any precondition for calling it.

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