ChatCut

manage_timelines

Manage project timelines (sequences). The working target is the default for reads/edits; the user's view may differ. Exports require an explicit full timeline UUID.

Pass a full timelineId to preview_timeline, inspect_item, find_transcript, manage_markers, split_item, detach_audio, edit_track, submit_export, or each edit_item entry to target one call without changing the working target or user's view. Use switch to retarget later calls; legacy clients also change the user's view.

Actions:

list: all timelines and which is the working target.
create: fresh timeline with a default video track, to build from the Media Pool. Composition inherits the working timeline; override with width/height or ratio ("W:H" such as "16:9", "9:16", "4:5"; short side 1080 px). Create several in one call via timelines (array of {name, ratio, width, height}).
duplicate: full copy of timelineId (tracks, items, markers, captions incl. word-level edits), to start from existing content (versions, cut-downs); its script is immediately editable.
switch: make timelineId the working target for later calls. A hidden timeline can't be selected; restore it first (update hidden=false).
update: rename (name), resize (width/height/ratio), and/or hide/restore (hidden) timelineId, defaulting to the working timeline. On resize, fit "contain" keeps everything visible, "cover" fills the frame. Hiding keeps the data but removes the tab.
delete: remove timelineId, or several atomically via timelineIds. A project keeps at least one timeline.

create/duplicate make the new timeline the working target (batch create: the last entry); pass activate=false to keep the current one. Name collisions auto-suffix "(2)". Use ratio OR width/height; custom dimensions must omit ratio.

Returns JSON timeline objects: {id, name, width, height, active, hidden}. All timeline IDs are full UUIDs; pass the listed id directly to submit_export.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "manage_timelines"
  }
}

Input Schema

Name	Required	Description
`fit`	No	update: how existing items adapt to a new canvas size. "contain" keeps everything visible, "cover" fills the frame.
`name`	No	Timeline name for create/duplicate; new name for update
`ratio`	No	Aspect ratio for create/update as "W:H" with positive whole numbers from 9:64 to 64:9, e.g. "16:9", "9:16", "1:1", "4:5", "21:9". The short side becomes 1080 px (16:9 is 1920x1080, 4:5 is 1080x1350). For any other size, pass width/height instead.
`width`	No	Composition width in pixels for create/update
`action`	Yes	list, create, duplicate, switch, update, or delete
`height`	No	Composition height in pixels for create/update
`hidden`	No	update: true hides the timeline (its tab disappears for everyone but data is kept; restorable), false restores it. The last visible timeline cannot be hidden.
`activate`	No	create/duplicate: false to keep the current active timeline. Defaults to true.
`projectId`	No	Project for this call (full ID or unambiguous prefix). Explicit-timeline calls never change the target of later calls; legacy project selection applies otherwise.
`timelines`	No	create: specs for creating several timelines in one call; each entry takes name/ratio/width/height and inherits unset composition from the active timeline. Top-level activate applies to the last entry.
`timelineId`	No	Target full timeline UUID from action=list (required for duplicate/switch; delete takes this or timelineIds; optional for update, which defaults to the working timeline)
`timelineIds`	No	delete: several full timeline UUIDs from action=list, removed atomically in one call.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedNov 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Beyond the annotations, the description discloses real side effects: create/duplicate make the new timeline the working target (last entry in a batch), switch changes it for later calls, legacy clients also change the user's view, delete is atomic across timelineIds, and a project must retain at least one timeline. Note that the tool contains a delete action while destructiveHint=false, but the description itself is accurate and in fact supplies the destructive-behavior context the annotation omits.

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

Conciseness4/5

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

The targeting rule is front-loaded before the action list, and the bullets are dense and scannable. It is long, and a few points (ratio vs width/height, auto-suffixing on name collisions) are restated in both the prose and the per-action bullets, costing some tightness.

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?

For a 12-parameter, six-action tool with no output schema, the description covers targeting semantics, per-action behavior, defaults, constraints (last timeline cannot be deleted or hidden), and even the returned timeline object shape {id, name, width, height, active, hidden}. An agent can call every action correctly from this text alone.

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%, so the schema already documents all 12 parameters, which sets the baseline at 3. The description does add some meaning on top — ratio's short-side-1080 rule, the requirement to omit ratio with custom width/height, which actions require timelineId, and inheritance of unset composition in the timelines array — but much of this also appears in the schema descriptions.

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?

The opening line gives a specific verb and resource ("Manage project timelines (sequences)") and the bulleted action list enumerates exactly what each of list/create/duplicate/switch/update/delete does. It distinguishes itself from siblings by naming preview_timeline, inspect_item, find_transcript, manage_markers, split_item, detach_audio, edit_track, submit_export and edit_item as callers that accept a timelineId rather than owners of timeline state.

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?

Explicit routing rules: pass a full timelineId for one-off targeting without changing the working target, use switch to retarget later calls, use update hidden=false before selecting a hidden timeline, use ratio OR width/height (custom dimensions must omit ratio), and pass activate=false to avoid retargeting on create/duplicate. Alternatives and exclusions are both stated.

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

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