Skip to main content
Glama

Merge video clips

video_merge
Destructive

Concatenate two or more video clips in order into a single rendered file, with optional transitions and output path control. Returns JSON success status and output path.

Instructions

Concatenate two or more video clips, in order, into one rendered file. Returns JSON {success, output_path}.

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": "video_merge"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipsYesOrdered absolute paths to existing video clips. Provide at least two clips; inputs are validated and never modified.
reviewNo
overwriteNoAllow replacing existing media files.
transitionNoxfade transition for every clip boundary, e.g. fade, dissolve, wipeleft, slideright.
output_pathNoDestination video path. Auto-generated when omitted; an existing supplied path may be overwritten.
transitionsNoOptional per-boundary xfade transitions. Overrides transition when provided.
transition_durationNoDuration in seconds for each transition; must fit inside neighboring clips.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / review
      Added value: +{
      +  "default": true,
      +  "type": "boolean"
      +}
  2. Changed10 schema fields changedv2.0.0
    • removedInput schema / properties / clips / title
      Removed value: -"Clips"
    • removedInput schema / properties / output_path / title
      Removed value: -"Output Path"
    • changedInput schema / properties / overwrite / description
      Previous value: -"Explicitly allow replacing existing media. Existing non-media files are protected."New value: +"Allow replacing existing media files."
    • removedInput schema / properties / overwrite / title
      Removed value: -"Overwrite"
    • changedInput schema / properties / transition / description
      Previous value: -"Optional xfade transition applied to every clip boundary, such as fade, dissolve, wipeleft, wiperight, slideleft, or slideright."New value: +"xfade transition for every clip boundary, e.g. fade, dissolve, wipeleft, slideright."
    • removedInput schema / properties / transition / title
      Removed value: -"Transition"
    • removedInput schema / properties / transition_duration / title
      Removed value: -"Transition Duration"
    • removedInput schema / properties / transitions / title
      Removed value: -"Transitions"
    • removedInput schema / title
      Removed value: -"video_mergeArguments"
    • removedOutput schema / title
      Removed value: -"video_mergeDictOutput"
  3. Changed1 schema field changedv1.16.4
    • addedInput schema / properties / overwrite
      Added value: +{
      +  "default": false,
      +  "description": "Explicitly allow replacing existing media. Existing non-media files are protected.",
      +  "title": "Overwrite",
      +  "type": "boolean"
      +}
  4. Changed1 schema field changedv1.16.0
    • addedInput schema / additionalProperties
      Added value: +false
  5. Changed5 schema fields changedv1.5.1
    • addedInput schema / properties / clips / description
      Added value: +"Ordered absolute paths to existing video clips. Provide at least two clips; inputs are validated and never modified."
    • addedInput schema / properties / output_path / description
      Added value: +"Destination video path. Auto-generated when omitted; an existing supplied path may be overwritten."
    • addedInput schema / properties / transition / description
      Added value: +"Optional xfade transition applied to every clip boundary, such as fade, dissolve, wipeleft, wiperight, slideleft, or slideright."
    • addedInput schema / properties / transition_duration / description
      Added value: +"Duration in seconds for each transition; must fit inside neighboring clips."
    • addedInput schema / properties / transitions / description
      Added value: +"Optional per-boundary xfade transitions. Overrides transition when provided."
  6. First observedv0.2.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, readOnlyHint=false, idempotentHint=false, so the safety profile is covered structurally. The description adds that output is a "rendered file" (implying processing cost) but never discloses the destructive surface itself — that existing media may be overwritten, or that a review step (default true) gates execution. Against annotations that already flag destructiveness, this is adequate but thin.

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?

Two short sentences, front-loaded with the core action, with no filler. The trailing "Returns JSON {success, output_path}" is slightly wasted since an output schema already exists, but it costs only a clause.

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 7-parameter destructive rendering tool, the description should at minimum warn that overwriting can replace existing media and explain what the undocumented `review` flag does (it has no schema description either). Return values are covered by the output schema, so that omission is fine, but the destructive and review-gating gaps remain.

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 86%, so the schema already documents clips, overwrite, transition, output_path, transitions, and transition_duration. The description's "two or more clips, in order" only restates the clips constraint and adds no format, ordering, or precedence detail beyond the schema. 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?

"Concatenate two or more video clips, in order, into one rendered file" gives a specific verb (concatenate), a specific resource (video clips), and an output shape (single rendered file). This clearly separates it from siblings like video_trim or video_extract_frame, though it never names or explicitly contrasts with any sibling.

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 description embeds a precondition ("two or more clips, in order") which implies when the tool applies, but it offers no when-not guidance and no pointer to alternatives for related tasks such as trimming first or adding audio. Usage is implied rather than stated.

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