Skip to main content
Glama

Apply transition

apply_transition

Apply a named transition between two adjacent clips and commit the edit immediately, rejecting unknown transition names before changes are made.

Instructions

Deterministic edit: apply a named transition between two adjacent clips, committed immediately (the same operation as the editor's transition picker). type is one of ~170 names, e.g. fade, cross_dissolve, dip_to_black, slide_left, push_left, wipe_left, zoom_in, whip_pan, light_leak, glitch, zoom_blur, page_curl, crt_power_off. An unknown name is rejected with the reason. Both layer ids must exist in the project. object_match_cut and parallax_occlusion need face tracking and are refused here — ask autonomous_edit for those.

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": {
      "project_id": "<project_id>",
      "type": "<type>",
      "to_layer_id": "<to_layer_id>"
    },
    "name": "apply_transition"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesTransition name.
easingNoOptional easing name.
directionNoOptional direction for directional transitions (e.g. left, right, up, down).
project_idYesProject whose committed scene is edited.
to_layer_idYesThe incoming clip (the transition plays into it).
duration_secNoOptional duration in seconds.
from_layer_idNoOptional outgoing clip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, closed-world; the description adds real behavior: edits are deterministic and committed immediately with no preview step, unknown names are rejected with a reason, and specific transitions are hard-refused. It stops short of saying what happens if a transition already exists at that cut point.

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?

Front-loaded with the core behavior, then preconditions, then the escape hatch to a sibling. The long example list is dense but functional, since name discovery matters for a free-string parameter with no enum.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Strong on inputs and refusals, but for a 7-parameter mutation with no output schema it says nothing about the returned result or what happens to a pre-existing transition at the same cut, leaving an agent to infer the outcome of a committed write.

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 baseline is 3; the description goes beyond it by describing the type vocabulary (~170 names with 13 concrete examples spanning fade, whip_pan, glitch, etc.) and by noting which names are unsupported, which the "Transition name" schema label does not convey.

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 ("apply a named transition between two adjacent clips") plus the key qualifier "committed immediately" and "deterministic edit," which separates it from the broader autonomous/queued siblings.

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?

Gives explicit exclusions and a named alternative: object_match_cut and parallax_occlusion are "refused here — ask autonomous_edit for those," with the reason (face tracking). It also anchors the operation to the editor's transition picker and states the precondition that both layer ids must exist.

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