Skip to main content
Glama

add_transition

Apply a transition at a clip edge or between two clips to create a two-sided edit point; choose video or audio effects, duration, alignment, and parameters.

Instructions

Apply a transition at a clip's edge (default: Cross Dissolve for video, Constant Power for audio). An edit point between two clips gets a two-sided transition.

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": {
      "clip": "<clip>"
    },
    "name": "add_transition"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipYesTimeline clip id (from list_timeline)
edgeNoWhich edge; omit for the nearest edit
alignNo
audioNoApply an audio transition instead
effectNoe.g. "Cross Dissolve", "Dip to Black", "Film Dissolve"
framesNoDuration in frames (default: the app's default, 1 s)
paramsNoTransition parameters, e.g. {"color": [1, 0.5, 0.15, 1], "amount": 100} for light_leak
projectNoPath to the .fcproj project file; omit to edit the FilmCraft app connected with connect_app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and openWorldHint=false, so the agent already knows this is a local mutation. The description adds useful behavior beyond that (default effect per media type, two-sided transitions at edit points), but says nothing about overwriting an existing transition, permission needs, or whether the operation is reversible.

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?

Two short sentences with the core action and the default behavior front-loaded. The second sentence about two-sided transitions is slightly terse but does earn its place by clarifying edge semantics.

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?

For an 8-parameter mutation with a nested object and no output schema, the description covers the core action and defaults but leaves 'align', the 'params' structure, and the project-vs-connected-app choice to the schema. Adequate but with clear gaps for a tool of this complexity.

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 description coverage is 88%, so the schema already documents most parameters, including defaults for 'effect' and 'frames'. The description echoes the defaults at a high level but adds no syntax or meaning for the undocumented 'align' enum or the nested 'params' object beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 transition at a clip's edge') and adds the default effect types per media kind. It does not, however, distinguish itself from siblings like 'fade' or 'apply_effect', which an agent could plausibly confuse with this tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the description establishes that transitions go at clip edges and that two-clip edit points get two-sided transitions, which hints at when the tool applies. There is no explicit when-to-use vs. 'fade'/'apply_effect' guidance and no stated prerequisites or exclusions.

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