Skip to main content
Glama

Assemble Highlights

assemble_highlights
Destructive

Stitch clips and title cards into one video using cuts or xfade transitions, even when sources differ in size, fps, or audio.

Instructions

Stitch clips (including title cards) into one video with cuts or xfade transitions; they need not match in size, fps, or audio.

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": {
      "clips": "<clips>"
    },
    "name": "assemble_highlights"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNoCommon output fps (default 30).
clipsYesClip paths, in order.
widthNoCommon output width (default 1920).
heightNoCommon output height (default 1080).
outputNoOptional output path. Defaults under SCREENCAST_HOME/edits.
durationNoTransition seconds (default 1).
overwriteNoAllow replacing an existing file at the output path (default false).
transitionNocut (default) or an xfade name (fade, wipeleft, slideup, ...).

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 / clips / description
      Previous value: -"Two or more clip paths, in order. Clips are auto-normalized, so they need not match."New value: +"Clip paths, in order."
    • changedInput schema / properties / duration / description
      Previous value: -"Transition length in seconds when not a cut (default 1)."New value: +"Transition seconds (default 1)."
    • changedInput schema / properties / transition / description
      Previous value: -"'cut' (default, hard cuts) or an xfade transition name (fade, wipeleft, slideup, ...)."New value: +"cut (default) or an xfade name (fade, wipeleft, slideup, ...)."
    • 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

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a write operation. The description adds useful context that inputs need not match in size, fps, or audio, which is beyond the schema. But it does not mention overwrite behavior or that it creates a new file at the output path, leaving some behavioral gaps for a destructive tool.

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?

A single, front-loaded sentence with no wasted words. It conveys the core action and a key differentiator efficiently.

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?

Given rich annotations, a complete input schema, and an output schema, the description covers the main purpose and a key constraint (heterogeneous inputs). Minor gap: it does not mention the overwrite/destructive aspect, but that is partially covered by annotations and the overwrite parameter description.

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%, so all parameters are documented in the schema. The description adds no additional meaning about parameters beyond what the schema provides; baseline 3 is appropriate.

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 ('stitch') and resource ('clips into one video'), and notes it handles title cards and heterogeneous inputs. However, it does not explicitly name the sibling tool concat, which likely handles similar stitching with matching properties, so sibling differentiation is only implied.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus concat or xfade_transition, nor any exclusions or prerequisites. The mention of cuts or xfade transitions is about capability, not selection criteria.

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