Skip to main content
Glama

Crossfade Transition

xfade_transition
Destructive

Join two videos with an xfade transition and crossfaded audio, even when their size, frame rate, or audio settings differ.

Instructions

Join two videos with an xfade transition (audio crossfaded); they need not match in size, fps, or audio. For more clips use assemble_highlights.

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": {
      "inputA": "<inputA>",
      "inputB": "<inputB>"
    },
    "name": "xfade_transition"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputAYesOutgoing video.
inputBYesIncoming video.
outputNoOptional output path. Defaults under SCREENCAST_HOME/edits.
durationNoTransition length in seconds (default 1).
overwriteNoAllow replacing an existing file at the output path (default false).
transitionNoxfade name (default fade): fade, wipeleft, slideup, circleopen, dissolve, ...

Output Schema

NameRequiredDescriptionDefault
outputPathYesPath of the file written.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.47.0
    • changedInput schema / properties / inputA / description
      Previous value: -"Path to the first (outgoing) video."New value: +"Outgoing video."
    • changedInput schema / properties / inputB / description
      Previous value: -"Path to the second (incoming) video."New value: +"Incoming video."
    • changedInput schema / properties / transition / description
      Previous value: -"xfade transition name (default fade): fade, wipeleft, slideup, circleopen, dissolve, ..."New value: +"xfade name (default fade): fade, wipeleft, slideup, circleopen, dissolve, ..."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "outputPath": {
      +      "description": "Path of the file written.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "outputPath"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.32.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnly=false, so the write semantics are covered; the description adds genuinely new context that the annotations cannot: audio is crossfaded, and inputs need not match in size, fps, or audio. That tolerance statement is the key operational fact for this tool and is stated plainly. It stops short of noting that the existing output file may be replaced, which is the residual destructive-behavior gap.

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?

Two short clauses and one routing sentence, no filler. The core operation and the audio detail are front-loaded, and the sibling routing is held to the end where it belongs.

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?

Output schema exists, so return values need no explanation, and annotations cover the destructive profile. The description supplies the tolerance and audio-crossfade behavior an agent needs before invoking. Slight gap: no mention of what happens to an existing output path, which matters for a destructive tool.

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 100% and every parameter is documented in-schema including defaults (duration 1, overwrite false, transition fade). The description adds nothing about parameters beyond the implicit point that no audio-matching parameter is needed. Baseline 3 is correct when the schema carries this load.

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?

Specific verb plus resource ('Join two videos with an xfade transition') with an explicit scope limit ('two videos') and a named transition mechanism. The parenthetical '(audio crossfaded)' disambiguates it from a plain concatenation, so an agent can tell it apart from concat/assemble_highlights without opening the schema.

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?

Explicitly routes multi-clip work away: 'For more clips use assemble_highlights.' That is a clear alternative with a selecting condition. It does not, however, address the nearest ambiguous sibling, concat, so an agent choosing between a hard cut join and a crossfade join still has to infer the distinction.

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