Skip to main content
Glama

Compose Videos

compose
Destructive

Lay 2-9 videos out side by side, stacked, or in a grid (before/after, app and terminal), labelled and in sync.

Instructions

Lay 2-9 videos out side by side, stacked, or in a grid (before/after, app and terminal), labelled and in sync.

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": {
      "inputs": "<inputs>"
    },
    "name": "compose"
  }
}

Input Schema

NameRequiredDescriptionDefault
audioNoInput index whose audio to keep (default 0), "mix", or "none".
inputsYesVideos in reading order, each with an optional label (e.g. "Before").
layoutNoside_by_side (default), stack, or grid.
outputNoOptional output path. Defaults under SCREENCAST_HOME/edits.
endWithNolongest (default; shorter ones hold their last frame) or shortest.
overwriteNoAllow replacing an existing file at the output path (default false).
alignMarkerNoLine inputs up on this add_marker label.

Output Schema

NameRequiredDescriptionDefault
outputPathYesPath of the file written.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.51.1

TDQS

A3.6/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 write/overwrite risk is signaled structurally. The description adds real context with 'labelled and in sync' (labels and marker-based alignment), but says nothing about what happens to the output path, existing files, or audio behavior beyond what annotations and schema already convey.

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 dense sentence that front-loads the core action and count constraint, then the layout options, then the use cases. Nothing is repeated and nothing is wasted.

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?

With an output schema present, return values need not be explained, and all seven parameters are fully described in the schema. What remains thin is routing: the description never positions this against sequential-combine siblings such as concat, which is the one gap an agent could trip on.

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 every one of the seven parameters, including enum meanings for layout and endWith, is already documented in the schema. The description reinforces the 2-9 input range and the 'in sync' intent behind alignMarker but adds no syntax or format detail beyond the schema.

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?

The description gives a specific verb ('lay out') plus resource ('2-9 videos') and enumerates the concrete layouts (side by side, stacked, grid), so an agent knows exactly what the tool produces. It stops short of naming a sibling like concat or assemble_highlights to distinguish sequential joining from spatial composition.

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?

The parenthetical use cases ('before/after, app and terminal') imply when this is the right tool, giving a usable mental model. However, there is no explicit when-not guidance and no reference to concat or assemble_highlights, so the agent must infer the boundary itself.

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