Skip to main content
Glama

Load timeline

timeline.load
Idempotent

Restore a timeline from the document timeline.get returned, e.g. after it expired (24 h after last use). Its media must still be here: media expires 7 days after last use, so import saved files again with media.import and swap them in with clip.replace.

Input Schema

NameRequiredDescriptionDefault
timelineYesA timeline as returned by timeline.get

Output Schema

NameRequiredDescriptionDefault
timeline_idYesTimeline handle; every edit returns a new one

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / timeline / properties / tracks / items / properties / clips / items / properties / spans
      Added value: +{
      +  "description": "Styled runs, as text.set spans takes them",
      +  "items": {
      +    "additionalProperties": {},
      +    "propertyNames": {
      +      "type": "string"
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare it non-read-only, idempotent, non-destructive, and closed-world. The description adds important expiration semantics for both timelines and media, though it does not explain whether loading replaces the active timeline or what happens on conflicts.

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?

Two tightly written sentences with the restore purpose and expiration caveat front-loaded. Every sentence adds operational value with no wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the rich input schema, output schema, and annotations, the description is complete enough to call correctly. It covers the key operational failure mode: expired media requiring re-import and clip replacement.

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 sole parameter has 100% schema coverage, so the baseline is 3. The description adds meaningful provenance and a precondition beyond the schema by saying it must be a document previously returned by timeline.get and that referenced media must still exist.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb, 'Restore', and resource, 'timeline', and identifies the source document as the one returned by timeline.get. This clearly distinguishes it from timeline.create and timeline.get without needing the schema.

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

Usage Guidelines5/5

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

Explicitly says when to use it: after a timeline expires 24 hours after last use. It also gives the fallback workflow when media has expired, naming media.import and clip.replace as alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.