Skip to main content
Glama

timeline_get

Read-only

Retrieve a saved video editing timeline—either the latest or a specific version—to review and revise it before saving changes.

Instructions

Read a saved timeline (latest or a given version) so you can revise it: change what the user asked, then timeline_validate saves the next version.

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
nameNo
versionNo
projectIdNo
timelineIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description stays consistent with that while adding real context: omitting a version yields the latest, and this tool itself does not persist anything — the save happens in timeline_validate. It does not describe what a missing name/timelineId or a nonexistent version produces, which is the main remaining unknown.

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?

One tight sentence with the resource and version scope front-loaded and the follow-up mutation step named at the end. No filler, no repetition of the tool name.

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?

The purpose and workflow loop are covered, which is what an agent most needs to choose this tool. But with four undocumented parameters and no output schema, the description should say what identifies the timeline and roughly what a read returns; that it does not leaves a meaningful gap before invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the load, and it only clarifies 'version' (omit for latest, otherwise a specific one). It never explains how 'name', 'projectId', and 'timelineId' relate — which one actually identifies the timeline, or whether 'name' alone is sufficient — leaving the agent to guess at lookup semantics.

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 ('Read a saved timeline') plus scope ('latest or a given version'), which is far more than a restatement of the name. It also positions itself against timeline_validate as the read side of an edit loop, so an agent can tell it apart from the writer sibling without opening a schema.

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

Usage Guidelines4/5

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

Gives an explicit workflow: use this to fetch the timeline so you can revise it, change what the user asked, then hand off to timeline_validate to persist the next version. There is no when-not guidance (e.g. use frames_get or analysis_get for narrower reads), but the primary usage context is unambiguous.

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