Skip to main content
Glama

Join clips

join_clips

Join two to six clips into one at the format's size, with a cut or a short crossfade, e.g. a lifestyle shot then the real app on screen. Trim each with start and end. Picture only: add the voice and music in render_video. 5 credits. Returns a task_id at once; follow with get_task.

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

Input Schema

NameRequiredDescriptionDefault
clipsYesIn order, e.g. the lifestyle shot, then the app on screen
formatYes
brand_idNoA brand kit from list_brands (id or name). Brings the colours, fonts, logo, website and default copy (headline, call to action, small print); use instead of brand.
transitionNoCrossfade seconds between clips; 0 for a straight cut

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only supply generic hints (openWorld, not idempotent, not destructive); the description adds substantive context they do not cover: cost (5 credits), asynchronous behavior ('returns a task_id at once; follow with get_task'), and the critical constraint that no audio is produced. It stops short of describing failure modes or how repeated calls create separate jobs, but the operational picture is largely complete.

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?

Front-loaded with the core action and constraints, then cost and async follow-up. The telegraphic fragments are dense but each carries information; only the example clause is arguably optional.

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?

For a 4-parameter async mutation with no output schema, the description covers inputs, cost, and the required follow-up call (get_task), which is what an agent needs to complete the workflow. Minor gaps remain around what happens on partial failure or how the returned task_id should be polled.

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 75%, so most parameters are already documented, and the description only reinforces clip trimming ('start and end') and the cut-vs-crossfade meaning of transition. It adds little about format's dimensional effect or brand_id's inheritance behavior beyond what the schema states.

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 (join), the resource (clips), the bounded input size (two to six) and the output framing (at the format's size). It also delimits scope with 'Picture only' and routes audio work to render_video, so an agent can distinguish it from siblings without opening a schema.

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?

Gives a concrete usage scenario ('a lifestyle shot then the real app on screen') and names the alternative for the excluded case (add voice and music in render_video). It does not spell out when not to join at all, but the picture-only boundary provides clear routing context.

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.

Resources