Skip to main content
Glama

video_stitch

Combine finished video clips into one ordered file with hard cuts, preserving each clip's audio. Optionally add voiceover, background music, or subtitles to assemble a longer video from separate clips.

Instructions

Join finished video clips into one file, in the order given, with a hard cut between each and each clip's audio kept — this assembles existing clips, it does not generate new video. Use it to build a video longer than a single model clip: generate the shots with video_generate, then stitch them. Do NOT use it for a single clip, or for a batch of clips meant to stay separate. Three optional layers, each its own parameter: lay a voiceover over the picture (pass narration — ONE take per clip, in clip order, NOT one joined track; each take is aligned to its own clip so nothing drifts), lay a background-music track under the whole thing (pass music), or burn in subtitles from an SRT file (pass subtitles); clips of different sizes are scaled to a common frame. Returns the output file path with its duration, resolution, and size, or a structured error with a hint. Requires ffmpeg on the system. Set dry_run=true to preview the plan without running anything.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clipsYesThe clips to join, in play order — local file paths (e.g. the `path` a video_generate result returns) or direct http(s) video URLs. At least two.
musicNoOptional audio file (a local path or a URL) laid under the whole video as background music, mixed below the clips' own audio.
outputNoOptional output file path. Omit to write a default filename into the media output directory.
dry_runNoIf true, return the planned output path and inputs; run no ffmpeg.
narrationNoOptional voiceover — ONE audio take per clip, in the same order and the same count as `clips`. Each take is padded with silence to its clip's length, so take N is heard over clip N with no timecodes to keep in sync. The narration sits at full level and the clips' own audio is ducked beneath it. A take longer than the clip it belongs to is an error naming that clip, never a truncation — shorten the line and re-voice that one take.
subtitlesNoOptional SRT subtitle file (a local path or a URL) burned into the video.
Install Server

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses key behaviors: hard cuts, audio kept, scaling of different-sized clips, narration alignment per clip, music mixing, subtitle burning, dry_run behavior, and ffmpeg requirement. It also mentions error handling for narration takes longer than clips. The only minor gap is not explicitly stating that the operation is non-destructive to input files, but the description is quite thorough.

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?

The description is dense but well-structured. It front-loads the core purpose, then provides usage guidance, then details optional parameters, then return value and requirements. Every sentence adds value. It's slightly long but justified given the complexity of the narration parameter. The structure is logical and scannable.

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

Completeness5/5

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

Given the tool's complexity (6 parameters, optional layers, alignment semantics, error conditions), the description is remarkably complete. It covers all parameters, explains the return value, mentions the ffmpeg dependency, and provides dry_run behavior. No output schema exists, so the description's mention of return fields ('path' with duration, resolution, size) is essential and provided. This is a model description.

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 description coverage is 100%, so the baseline is 3. The description adds significant value beyond the schema: it explains the narration alignment model ('ONE take per clip, in clip order, NOT one joined track; each take is aligned to its own clip so nothing drifts'), the ducking behavior, and the error condition for long takes. It also clarifies the clips parameter accepts paths or URLs. This goes well beyond the schema's basic descriptions.

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?

The description clearly states the tool's purpose: 'Join finished video clips into one file, in the order given, with a hard cut between each and each clip's audio kept'. It specifies the verb (join), resource (video clips), and key behaviors (order, hard cut, audio kept). It also distinguishes from video_generate by explicitly stating 'this assembles existing clips, it does not generate new video'.

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?

The description provides explicit when-to-use guidance: 'Use it to build a video longer than a single model clip: generate the shots with video_generate, then stitch them.' It also gives clear exclusions: 'Do NOT use it for a single clip, or for a batch of clips meant to stay separate.' This is exemplary usage guidance.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/SupercmoHQ/superCMO-skills'

If you have feedback or need assistance with the MCP directory API, please join our Discord server