Skip to main content
Glama

clips_assemble

Build a sequence by appending clip segments back-to-back on a track with optional gaps, ideal for transcript-based cuts. Each segment references media with optional in/out points; in/out omitted = whole clip.

Instructions

Build a sequence: append segments back-to-back on track (video+linked audio), starting at start (default: end of the track) with optional gap seconds between. Segment = {"media": ref, "in": src_sec, "out": src_sec} (in/out optional = whole clip), may override "type"/"track". Perfect for transcript-based cuts.

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": {
      "segments": "<segments>"
    },
    "name": "clips_assemble"
  }
}

Input Schema

NameRequiredDescriptionDefault
gapNo
startNo
trackNoV1
segmentsYes
audio_trackNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden. It does disclose useful traits (video plus linked audio, default start at end of track, gap insertion), but says nothing about what happens to existing content on the target track, whether the operation is destructive or rippling, error behavior, or permissions.

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?

Dense and front-loaded: the core operation comes first, followed by parameter defaults and an inline segment shape example. Nearly every clause earns its place, though the compressed parenthetical style demands careful reading.

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 five-parameter tool with nested free-form segment objects and no output schema or annotations, the description covers the core mechanics well. It falls short on the audio_track parameter and on side effects or return information, which matter for an assembly operation that alters a track.

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 must compensate, and it largely does: track, start, gap, and the segments structure with media/in/out and optional type/track overrides are all explained meaningfully. However, the audio_track parameter is never mentioned, leaving one of five parameters undocumented anywhere.

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 resource: appends multiple segments back-to-back on a track to build a sequence. The segment semantics and the 'transcript-based cuts' framing make the operation concrete and distinct from single-clip placement, though no sibling is named explicitly.

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?

'Perfect for transcript-based cuts' implies the intended workflow, and the default start (end of track) hints at append-style usage. There is no explicit when-not guidance or named alternative such as clips_place for single clips, so usage is only implied.

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