switch

Read Editor Timeline

read_editor_timeline

Read-onlyIdempotent

Read the timeline of your Editor project (or one shared with you) track by track: every clip with its index, label, start, end, length, in and out points in its file, link, speed, volume and fades; the project's media (ids and names to place), its text layers, its colour look, the motion blocks and film stocks that exist; and check, the things to look at before an export (a clip playing past the end of its file, a clip with no file or no length, clips overlapping on a track, a mix that could clip, words running past the video, black gaps, unused media), each with its second and clip. Also every timeline tab of the project (id, name, open or not, length) and the project's shape. The media list only with include_media true; readback summary gives track lengths and clip counts only. Fix every warning in check before you say the edit is done. The loudness note (mix.peak) is a worst-case guess the export limiter already holds at -1 dB: report it and leave it to the creator. Free. Call it before and after edit_editor_timeline so you know the indexes and ids.

Input Schema

Name	Required	Description
`readback`	No	How much timeline comes back. full: every track and clip. changes: only the tracks this call changed. summary: each track's clip count and end. Fields left out are empty or at their default (speed 1, volume 0 dB, no fades, enabled). Default full.
`timeline`	No	Which timeline tab to read, by name or id. Default: the open tab.
`project_id`	Yes	The Editor project id (list_editor_projects).
`include_media`	No	Also list the project media (ids and names to place). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 22, 2026

addedInput schema / properties / include_media

Added value: +{
+  "description": "Also list the project media (ids and names to place). Default false.",
+  "type": "boolean"
+}

addedInput schema / properties / readback

Added value: +{
+  "description": "How much timeline comes back. full: every track and clip. changes: only the tracks this call changed. summary: each track's clip count and end. Fields left out are empty or at their default (speed 1, volume 0 dB, no fades, enabled). Default full.",
+  "enum": [
+    "full",
+    "changes",
+    "summary"
+  ],
+  "type": "string"
+}

addedInput schema / properties / timeline

Added value: +{
+  "description": "Which timeline tab to read, by name or id. Default: the open tab.",
+  "type": "string"
+}

AddedOct 13, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, yet the description still adds real behavior: media list appears only with include_media true, summary readback returns only track lengths and clip counts, the check block enumerates the exact warning classes with their second/clip anchors, and it flags mix.peak as a worst-case estimate already held at -1 dB that should be reported, not fixed. That last caveat actively prevents an agent from over-correcting.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the payload section is one enormous run-on list strung together with semicolons and a malformed clause ('and check, the things to look at before an export'). The information is valuable but the structure makes it harder to parse than necessary.

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?

There is no output schema, so the description carries the full burden of describing the return value, and it does: tracks, clips with all fields, media, text layers, look, motion blocks, film stocks, tabs, warnings with positions, and the field-default convention. Nothing an agent needs to interpret the response is missing.

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 100%, so the baseline is 3, but the description adds cross-parameter context the schema states only locally: that include_media gates the media list and that readback=summary degrades to track lengths and clip counts. It does not add anything about the timeline tab selector beyond the schema's 'name or id'.

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 and resource ('Read the timeline of your Editor project ... track by track') and enumerates the concrete payload: clip index, label, start/end, in/out points, link, speed, volume, fades, media ids, text layers, look, motion blocks, film stocks, tabs and shape. This is clearly differentiated from get_editor_project (metadata) and premiere_read_timeline (different product).

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?

Explicitly instructs 'Call it before and after edit_editor_timeline so you know the indexes and ids' and 'Fix every warning in check before you say the edit is done', which gives strong sequencing context. It does not name when NOT to use it or point to a nearer alternative such as get_editor_project, so it stops short of full routing guidance.

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

All switch 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.

Resources

Need Help?