Skip to main content
Glama

Join shots into one clip

concat

Joins ordered gallery video IDs into one MP4 or WebM, matching shots to the first clip's size and frame rate, with optional fades, music, logo, and end card.

Instructions

Joins finished videos (gallery ids, in order) into one MP4 or WebM that appears in the gallery. Shots are matched to the first shot's size and frame rate; shots without sound get silence. fade: seconds of the transition between shots, 0 = hard cut.

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": {
      "ids": "<ids>"
    },
    "name": "concat"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
fadeNo
logoNoGallery id or absolute path of a PNG (transparency kept), shown over the whole clip
musicNoAbsolute path of an audio file (mp3, wav, m4a, aac, flac, ogg); trimmed to the clip, fades out at the end
formatNomp4 = H.264/AAC, plays everywhere; webm = VP9/Opus, royalty freemp4
endcardNoGallery id or absolute path of an image appended as the last shot
fade_inNoSeconds of fade from black at the start (picture and sound)
fade_outNoSeconds of fade to black at the end (picture and sound)
logo_scaleNoLogo width as a share of the video width
transitionNoKind of transition when fade > 0: fade = cross-dissolve, fadeblack/fadewhite = dip to black/white, wipeleft, slideleftfade
shot_volumeNoLevel of the shots' own sounds under the music
music_volumeNo
logo_positionNobr
endcard_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the load and delivers real behavioral detail: output lands in the gallery, shots are conformed to the first shot's size and frame rate, silent shots get padded silence, and fade=0 means a hard cut. It omits failure modes (invalid ids, mismatched inputs beyond size/fps) and any cost/duration or auth implications, which keeps it below a 5.

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?

Three tight sentences: purpose and output first, then a conforming/audio rule an agent would not otherwise know, then the fade edge case. No filler and nothing buried.

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 a 14-parameter, no-annotation, no-output-schema tool, the description covers the core behavior but stays silent on what is returned (gallery id of the new clip?), limits on input length, and error behavior for bad ids. Schema documents the individual parameters, so this is adequate rather than complete.

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 64%, so the schema already explains most parameters including logo, music, format, and transitions. The description adds meaning only for fade (seconds of transition, 0 = hard cut) and the ordering semantics of ids, leaving most of the 14 parameters to the schema.

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?

States a specific verb (joins), the resource (finished videos identified by gallery ids, in order) and the concrete result (one MP4 or WebM that appears in the gallery). That combination is unmistakable against siblings like generate or last_frame.

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 phrase 'finished videos' hints that inputs must be completed clips, and 'in order' tells the agent the id sequence is the timeline. But there is no explicit when-to-use/when-not guidance or routing to any alternative tool for other assembly needs.

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