Skip to main content
Glama

join_clips

Combine video clips in order into one video, with cut, fade-through-black, or crossfade transitions and configurable transition length.

Instructions

Clips into one video, in order. transition: cut | fade (through black) | crossfade; seconds = its length.

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": {
      "videos": "<videos>"
    },
    "name": "join_clips"
  }
}

Input Schema

NameRequiredDescriptionDefault
videosYes
secondsNo
transitionNocut

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already cover the safety profile: this tool writes results (readOnlyHint=false), produces an artifact (destructiveHint=false), and needs no external services (openWorldHint=false). The description adds real context about how transitions behave — 'fade (through black)' and 'crossfade' — but says nothing about whether clips must share resolution or codec, how audio is handled, or whether the input files are affected.

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?

It uses two short sentences with no wasted words, and leads with the main behavior before covering parameters. The telegraphic style ('Clips into one video') trims a little too far, removing the article, but the information density is good.

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?

It is reasonably complete for a three-parameter editing tool whose annotations are minimal and whose schema has no descriptions. However, it leaves out likely prerequisites — clips probably need matching resolution and audio handling is unstated — and it does not explain how ordering or the transition length apply.

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 0%, so the description carries the whole burden of explaining parameters. It defines values for transition that the schema leaves unset: the schema types transition as a raw string with no enum, while the description lists cut, fade and crossfade. It also explains that seconds is the transition length. However, it says nothing about the required videos parameter, beyond implying order, and nothing about parameter interactions.

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?

States a specific verb and result: joins clips into one video and preserves their order. That distinguishes it from single-clip tools like extend_clip or fade, but it never names an alternative for the multi-clip case (for example build_video), so differentiation depends on the reader inferring what the sibling names mean.

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?

Phrases like 'in order' hint at usage but there is no explicit when-to-use statement and no when-not-to-use statement. Nothing tells the agent whether this tool is the right one when it wants a multi-clip composition rather than a single-clip edit.

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