Skip to main content
Glama

Assemble video

assemble_video
Destructive

Join clips the account already has into ONE finished video, in the order given, optionally over a voiceover (narrationUrl) and a music bed, which become separate tracks with the clips ducked under the voice, and with burned-in captions. The bed is a track from the library (musicUrl) or one composed for this cut from a description (musicPrompt), never both. One clip plus a track is how to put music or narration under a single video: "add music to my video" is clipUrls [that video] with a musicPrompt, and no pipeline to build. Every url must come from list_assets or a run's outputs in get_run. A slideshow of photos or images, with a push-in, a pan or Ken Burns, is ONE call with the image urls, stillMotion and stillSeconds, never an image-to-video clip per photo. Stills hold 3 seconds each (or stillSeconds), or stretch so a longer voiceover plays in full. With no stills, the clips have to run as long as the voice (list_assets gives each durationSec): the last frame holds up to 3 seconds so the voice can finish, and a voice longer than that past the clips is refused with nothing charged. lengthSec in the result is how long the cut will run, and any warning in it should be passed on. Renders in the background: poll get_run with the returned pipelineId and runId. Free once the account has bought credits (the result carries charged: false), so never ask a paying account to top up before assembling; charged on a trial. The same request made again within a few minutes returns the render already started (repeat: true) rather than starting another; to render the same cut a second time on purpose, pass a new requestId. Needs the pipelines:run and pipelines:write scopes.

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": {
      "clipUrls": "<clipUrls>"
    },
    "name": "assemble_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoWhat to call the render, e.g. "Beach trip cut".
captionsNoTranscribe the finished edit and burn captions in. Only worth it when the clips or narration contain speech.
clipUrlsYesVideo or image urls in play order: two or more, or exactly one when narrationUrl, musicUrl or musicPrompt is set.
musicUrlNoMusic bed under the whole edit, beneath the clips' own sound and any narration: an audio url from list_assets. Leave it out when passing musicPrompt.
fadeInSecNoFade the opening up from black over this many seconds: the first shot's picture and the music bed together.
requestIdNoAny id you choose for this one request. A call with an id that already started a render returns that render; a new id renders again even when everything else is identical.
fadeOutSecNoFade the whole ending to black and silence over this many seconds: the last shot's picture eases down and the music bed fades with it. This is "fade out at the end"; 1.5 to 3 reads as a deliberate ending. The transition argument is the cut between shots and does not touch the ending.
transitionNoHow each shot hands off to the next: the join between two shots, applied at every cut. Defaults to a hard cut. "fadeblack" dips to black between shots; it is not a fade-out at the end, which is fadeOutSec.
callbackUrlNoAn https URL Treza POSTs the finished run to, once, when it ends (success, partial, error or cancelled), so an automation can wait for the render instead of polling get_run. The body is the JSON get_run returns for the run, sent with the headers X-Treza-Event: run.finished and X-Treza-Delivery: <runId>. It must be https on the default port and reach a public address; a URL that does not is refused before anything runs or is charged. Each attempt waits 10 seconds for a 2xx, and a timeout, 408, 429 or 5xx is retried twice more.
musicPromptNoCompose the music bed for this cut instead of taking one from the library: genre, mood, tempo and instruments, e.g. "calm cinematic ambient, soft piano, gentle pads, no vocals". It sits and ducks exactly like a musicUrl bed and takes the same fades. Written by the Audio Generation node's default model (get_node_type music-gen), or its full-song model when the cut runs past 30 seconds; the result names the model as composedMusic. Leave it out when passing musicUrl.
orientationNo"vertical" is 1080x1920 for Shorts, Reels and TikTok, "horizontal" is 1920x1080, "match_first" (the default) keeps the first clip's shape. Shots that do not fill the frame are letterboxed, never cropped.
stillMotionNoA slow camera move over every still image: push_in, pull_out, a drift across the photo (pan_left, pan_right, pan_up, pan_down), or ken_burns (a different move on each photo in turn). Video clips play as shot. Defaults to none.
narrationUrlNoVoiceover laid over the whole edit. Everything else ducks under it.
stillSecondsNoHow long each still image holds, in seconds. Defaults to 3; 3 to 5 reads well for a slideshow. A narrationUrl longer than the stills still plays in full: they stretch to cover it. Leave it out when the voice should set the pace of a cut that is all stills.
audioFadeInSecNoFade the music bed (or the only track) up over this many seconds at the start. Applies to a composed bed too.
audioFadeOutSecNoFade the music bed (or the only track) down over this many seconds at the end, with the picture left as it is; 2 to 4 reads as a deliberate ending. Narration is never faded when there is a bed. For the whole ending to fade, use fadeOutSec.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / clipUrls / maxItems
      Previous value: -12New value: +30
  2. Changed1 schema field changed
    • addedInput schema / properties / callbackUrl
      Added value: +{
      +  "description": "An https URL Treza POSTs the finished run to, once, when it ends (success, partial, error or cancelled), so an automation can wait for the render instead of polling get_run. The body is the JSON get_run returns for the run, sent with the headers X-Treza-Event: run.finished and X-Treza-Delivery: <runId>. It must be https on the default port and reach a public address; a URL that does not is refused before anything runs or is charged. Each attempt waits 10 seconds for a 2xx, and a timeout, 408, 429 or 5xx is retried twice more.",
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • addedInput schema / properties / stillMotion
      Added value: +{
      +  "description": "A slow camera move over every still image: push_in, pull_out, a drift across the photo (pan_left, pan_right, pan_up, pan_down), or ken_burns (a different move on each photo in turn). Video clips play as shot. Defaults to none.",
      +  "enum": [
      +    "none",
      +    "push_in",
      +    "pull_out",
      +    "pan_left",
      +    "pan_right",
      +    "pan_up",
      +    "pan_down",
      +    "ken_burns"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / stillSeconds
      Added value: +{
      +  "description": "How long each still image holds, in seconds. Defaults to 3; 3 to 5 reads well for a slideshow. A narrationUrl longer than the stills still plays in full: they stretch to cover it. Leave it out when the voice should set the pace of a cut that is all stills.",
      +  "maximum": 30,
      +  "minimum": 0.5,
      +  "type": "number"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / requestId
      Added value: +{
      +  "description": "Any id you choose for this one request. A call with an id that already started a render returns that render; a new id renders again even when everything else is identical.",
      +  "maxLength": 128,
      +  "minLength": 1,
      +  "type": "string"
      +}
  5. Changed4 schema fields changed
    • changedInput schema / properties / audioFadeOutSec / description
      Previous value: -"Fade the music bed (or the only track) down over this many seconds at the end; 2 to 4 reads as a deliberate ending. Narration is never faded when there is a bed."New value: +"Fade the music bed (or the only track) down over this many seconds at the end, with the picture left as it is; 2 to 4 reads as a deliberate ending. Narration is never faded when there is a bed. For the whole ending to fade, use fadeOutSec."
    • addedInput schema / properties / fadeInSec
      Added value: +{
      +  "description": "Fade the opening up from black over this many seconds: the first shot's picture and the music bed together.",
      +  "maximum": 30,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / fadeOutSec
      Added value: +{
      +  "description": "Fade the whole ending to black and silence over this many seconds: the last shot's picture eases down and the music bed fades with it. This is \"fade out at the end\"; 1.5 to 3 reads as a deliberate ending. The transition argument is the cut between shots and does not touch the ending.",
      +  "maximum": 30,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • changedInput schema / properties / transition / description
      Previous value: -"How each shot hands off to the next. Defaults to a hard cut."New value: +"How each shot hands off to the next: the join between two shots, applied at every cut. Defaults to a hard cut. \"fadeblack\" dips to black between shots; it is not a fade-out at the end, which is fadeOutSec."
  6. Changed4 schema fields changed
    • changedInput schema / properties / audioFadeInSec / description
      Previous value: -"Fade the music bed (or the only track) up over this many seconds at the start."New value: +"Fade the music bed (or the only track) up over this many seconds at the start. Applies to a composed bed too."
    • changedInput schema / properties / clipUrls / description
      Previous value: -"Video or image urls in play order: two or more, or exactly one when narrationUrl or musicUrl is set."New value: +"Video or image urls in play order: two or more, or exactly one when narrationUrl, musicUrl or musicPrompt is set."
    • addedInput schema / properties / musicPrompt
      Added value: +{
      +  "description": "Compose the music bed for this cut instead of taking one from the library: genre, mood, tempo and instruments, e.g. \"calm cinematic ambient, soft piano, gentle pads, no vocals\". It sits and ducks exactly like a musicUrl bed and takes the same fades. Written by the Audio Generation node's default model (get_node_type music-gen), or its full-song model when the cut runs past 30 seconds; the result names the model as composedMusic. Leave it out when passing musicUrl.",
      +  "maxLength": 1000,
      +  "type": "string"
      +}
    • changedInput schema / properties / musicUrl / description
      Previous value: -"Music bed under the whole edit, beneath the clips' own sound and any narration."New value: +"Music bed under the whole edit, beneath the clips' own sound and any narration: an audio url from list_assets. Leave it out when passing musicPrompt."
  7. Added

TDQS

A4.5/5.0
Behavior3/5

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

The description carries a lot beyond annotations: background rendering, billing (free once credits are bought, charged on trial, nothing charged on refusal), required scopes, and duplicate-request dedupe with requestId. However, that dedupe sits in tension with idempotentHint=false, and the destructiveHint=true write side is never spelled out (what an assembly overwrites or how assets are consumed). Useful, but partly ambiguous against the supplied hints.

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?

Purpose and the core recipes are front-loaded, and nearly every sentence carries operational information. The cost is density: one unbroken paragraph of 300+ words mixing purpose, slideshow rules, timing rules, billing, and scopes, which is harder to scan than it needs to be.

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?

For a 16-parameter, non-read-only render tool with no output schema, it covers what an agent needs: valid inputs, timing constraints, failure modes (refused narration mismatch), return fields (lengthSec, charged, repeat, pipelineId/runId), and async completion. Nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Though schema coverage is 100%, the description supplies cross-parameter meaning the schema cannot: musicUrl and musicPrompt are mutually exclusive, stills stretch to cover a longer narrationUrl, the last frame holds up to 3 seconds, and fadeOutSec is distinct from transition. These rules materially change how an agent fills 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?

Opens with a specific verb and resource: "Join clips the account already has into ONE finished video, in the order given." It scopes the tool further by carving out adjacent jobs (slideshow = one call with image urls; single clip + track = no pipeline to build), so an agent can tell it apart from pipeline-building or image-to-video routes.

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?

Gives explicit when-to-use recipes ("add music to my video" is clipUrls [that video] with a musicPrompt), explicit mutual exclusion (musicUrl vs musicPrompt, "never both"), and explicit boundaries (use fadeOutSec, not transition, for the ending). It also routes post-call behavior: poll get_run with pipelineId/runId, or use callbackUrl.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.