CutClip.one

timeline.remove_transitions

Remove transitions from several clips in ONE call (and one undo step): every transition whose clip(s) are all selected (itemIds, trackId or all:true, like timeline.add_transitions) — a crossfade/smooth_blend needs both its clips selected, a fade just its own clip. Crossfaded clips are shifted back to their pre-transition positions. Fails if there is nothing to remove.

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": {
      "projectId": "<projectId>",
      "expectedVersion": "<expectedVersion>"
    },
    "name": "timeline.remove_transitions"
  }
}

Input Schema

Name	Required	Description
`all`	No	Every clip on every track — narrow with trackType
`itemIds`	No	These specific clips
`trackId`	No	Every clip on this track
`projectId`	Yes
`trackType`	No	With all: only tracks of this type
`expectedVersion`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the single-undo-step behavior, that crossfaded clips are shifted back to pre-transition positions, and that the call fails when there is nothing to remove. It omits permission requirements and what the response contains, which keeps it short of a 5.

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?

Front-loaded with the batch benefit and undo behavior, then the selection rule, then the side effect and failure mode. Dense but every clause carries information; the parenthetical nesting makes it slightly harder to parse than it needs to be.

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?

For a 6-parameter mutation tool with no annotations and no output schema, the description covers selection semantics, side effects, and failure behavior well. The missing pieces are the meaning of expectedVersion (a concurrency token) and any indication of the return value.

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 67%, and the description compensates by explaining how itemIds, trackId, and all:true select clips, and by adding the non-obvious rule that a crossfade requires both clips selected while a fade needs only its own. projectId and expectedVersion are left unexplained, which is the main gap.

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 ('Remove transitions from several clips') plus the batch scope ('in ONE call'), which cleanly separates it from the singular timeline.remove_transition and from timeline.add_transitions.

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?

Explains the selection rule precisely (every transition whose clips are all selected) and gives the crossfade-vs-fade distinction, plus the failure condition when nothing matches. It does not explicitly contrast with the singular timeline.remove_transition, so the routing guidance is clear but not exhaustive.

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

All CutClip.one 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.