Skip to main content
Glama

Edit clips into one video

compose_video

Cut videos and pictures from earlier results into one finished MP4, in order, with optional music (your own track or a free library track), narration, sound effects, captions and a title. Pictures get a slow camera move. Free for OAuth and API keys: neither wallet is charged; this only edits existing media. Generate new media separately with USD approval for API keys. Takes about a minute; returns a link to the finished video.

Input Schema

NameRequiredDescriptionDefault
nameNoOptional file name for the finished video.
clipsYesThe pieces in order (1 to 30): popnow:// links to videos or pictures from earlier results.
titleNoOptional title shown big for the first 2.5 seconds.
music_urlNoOptional background music: a popnow:// link to a song or instrumental (for example from create_music).
sound_urlNoOptional sound effects or ambience: a popnow:// link from add_sound.
subtitlesNoOptional captions burned into the video, in time order.
mute_clipsNoSet true to drop the clips' own sound (keep only music, narration and sound_url).
transitionNoHow pieces join: cut (default) or crossfade.
music_trackNoOr a free PopNow library track instead of music_url: rising-tide, moonlit-reverie, banana-peel, last-letter, rain-on-glass, tightening-wire, neon-circuit or midnight-jazz.
aspect_ratioNo9:16 (phone, default), 16:9 (wide) or 1:1 (square). Pieces with another shape get borders.
voiceover_urlNoOptional narration: a popnow:// link from create_speech. Music is lowered while it plays.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / clips / type
      Previous value: -[
      -  "null",
      -  "array"
      -]New value: +"array"
    • changedInput schema / properties / subtitles / type
      Previous value: -[
      -  "null",
      -  "array"
      -]New value: +"array"
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description adds important behavioral context: composition is free for OAuth and API keys, neither wallet is charged, it only edits existing media, it takes about a minute, and it returns a link. These details materially help an agent understand cost, runtime, and output.

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?

The description is front-loaded with the core action and scope, followed by cost, runtime, and return behavior. Despite covering several important points, it remains tight and avoids unnecessary repetition.

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 an 11-parameter composition tool with no output schema, the description supplies the missing behavioral context: cost model, runtime, output link, and the boundary between editing existing media and generating new media. Combined with the fully documented schema, this is complete enough to call the tool correctly.

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 100%, so the input schema already explains all parameters, including clip motion, timing, music, subtitles, and transitions. The description adds little parameter-level detail beyond the schema, so the baseline score of 3 is appropriate.

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?

The description states a specific verb and resource: cutting videos and pictures from earlier results into one finished MP4, in order. It also explicitly contrasts this with generating new media, which helps distinguish it from sibling creation tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly says to use this when combining existing clips into one video, and explicitly warns that new media should be generated separately. However, it does not name specific alternatives such as create_video or edit_video, so the guidance is strong but not exhaustive.

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.