Skip to main content
Glama

Frapea

manage_transitions

Transitions on a track's cuts OR lone clip edges (a free head/tail takes a single-sided fade from/to nothing; its alignment is forced). action: 'add' (trackId + atFrame = the cut where one clip ends and the next starts, + type; optional durationFrames (default 30, clamped to the clips' source handles), alignment centered|start|end, params) | 'remove' (transitionId) | 'update' (transitionId + any of type/durationFrames/alignment/params). Types: crossDissolve, dipToBlack, dipToWhite, wipe (params.angle deg, params.softness 0-100), slide (params.angle), push (params.angle). Both clips need source material past the cut — a transition that cannot fit is refused; edits that break the cut remove it. Returns {ok, transitionId?}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoTransition type.
tokenYesThe session token `connect` returned. Pass it on every call — it says which browser to drive.
actionYesadd | remove | update
paramsNoType params patch (e.g. { angle: 90 }).
atFrameNoThe cut frame for 'add'.
trackIdYesTrack owning the cut (get_timeline).
alignmentNocentered | start | end
projectIdYesProject id from get_projects.
timelineIdYesTarget timeline.
transitionIdNoExisting transition id.
durationFramesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources