Skip to main content
Glama

Concatenate Videos

concat
Destructive

Join videos end to end with hard cuts: stream copy when compatible or re-encode when needed. Use for simple sequencing, not transitions.

Instructions

Join videos end to end with hard cuts: stream copy when they match, else a re-encode (mode says which). For transitions use xfade_transition or 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": {
      "inputs": "<inputs>"
    },
    "name": "concat"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYesVideo paths to join, in order.
outputNoOptional output path. Defaults under SCREENCAST_HOME/edits.
overwriteNoAllow replacing an existing file at the output path (default false).

Output Schema

NameRequiredDescriptionDefault
outputPathYesPath of the file written.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.47.0
    • changedInput schema / properties / inputs / description
      Previous value: -"Two or more video paths to join, in order. Matching inputs are stream-copied; others are re-encoded."New value: +"Video paths to join, in order."
    • 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. Changed1 schema field changedv0.39.0
    • changedInput schema / properties / inputs / description
      Previous value: -"Two or more video paths to join, in order. Inputs must share codec/format."New value: +"Two or more video paths to join, in order. Matching inputs are stream-copied; others are re-encoded."
  3. First observedv0.32.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context the annotations cannot: it explains the two execution paths (stream copy when inputs match, re-encode otherwise), which tells the agent results may differ in quality/speed depending on input compatibility. It stops short of saying what happens to an existing output file or whether re-encoding loses quality, keeping it out of 5 territory.

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 tightly packed sentences with zero filler: the core behavior first, the sibling routing second. Every clause carries information an agent needs.

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 no explanation, and the description covers purpose, execution modes, and alternatives. The remaining gap is the phantom `mode` reference, which leaves the agent guessing whether mode selection is automatic or exposed as a parameter.

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 coverage is 100%, so inputs/output/overwrite are already documented and the baseline is 3. The description does add meaning about `inputs` (matching inputs allow stream copy, mismatched ones force a re-encode), but it also references a `mode` parameter that does not exist in the schema — a misleading pointer an agent could act on and get an error.

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+resource ('Join videos end to end with hard cuts') and scopes it to hard cuts only, which immediately separates it from transition-based siblings. It names the exact alternatives (xfade_transition, assemble_highlights) an agent should consider instead, so the tool is distinguishable without opening any schema.

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?

Explicitly gives the alternative and the condition that selects it: 'For transitions use xfade_transition or assemble_highlights.' That is the classic when-not-use routing an agent needs, and it is stated rather than implied.

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