cuttingfloor

Get timeline

timeline.get

Read-onlyIdempotent

The full timeline: tracks, clips (frames, end exclusive), link groups and the media it uses. The server keeps a timeline 24 hours after last use: for work longer than a day, save this document on your side (it is the edit) and restore it with timeline.load.

Input Schema

Name	Required	Description	Default
`timeline_id`	Yes	Timeline handle; every edit returns a new one

Output Schema

Name	Required	Description
`name`	Yes
`media`	Yes
`master`	No
`nested`	No	Timelines nested as compound clips, at any depth: each has this shape without timeline_id, parent or nested
`parent`	Yes
`tracks`	Yes	Video tracks bottom to top, then audio tracks
`effects`	No	Effects on the whole picture and mix
`duration`	Yes	Timeline length in frames
`sequence`	Yes
`timeline_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026

addedOutput schema / 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"
+}

First observedOct 25, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond annotations that already mark this as a safe read, the description discloses a critical lifecycle behavior: timelines are retained for 24 hours after last use and must be saved externally for longer work. It also clarifies that frame end is exclusive, adding useful semantic detail.

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?

The description is two tight sentences with no wasted language. It front-loads what the timeline document contains and then adds the retention/restoration warning.

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 an output schema, full parameter schema coverage, and annotations covering safety, the description is nearly complete. Its main omission is explicit differentiation from sibling timeline inspection tools, though the retrieval scope is still clear enough to call correctly.

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

Parameters3/5

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

Schema coverage is 100%, and the sole timeline_id parameter is fully documented in the schema as a handle returned by edits. The description adds no parameter-specific detail beyond the schema, so baseline 3 is appropriate.

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 clearly states that this retrieves the full timeline, including tracks, clips, link groups, and media. It is specific about the returned document, but it does not explicitly distinguish itself from sibling timeline tools such as timeline.diff or timeline.history.

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?

The description implies retrieval use and gives important persistence guidance, including saving externally and restoring with timeline.load. However, it does not explicitly say when to use timeline.get instead of other timeline inspection tools like timeline.diff or timeline.history.

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

All cuttingfloor tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.