Skip to main content
Glama

Create auto montage

create_auto_montage

Scans a folder for clips and stills, builds a crossfade montage with auto-advance triggered by beat, bar, or interval, and exposes controls for playback, mode, and timing.

Instructions

Point at a folder and build a self-running clip montage: scans the folder for clips/stills, builds one Movie File In TOP per file feeding a Switch TOP (fractional-index crossfade) → Null TOP, and adds an auto-advance brain on top — a Beat CHOP (clock='beat' or 'bar' with division) or LFO CHOP (clock='interval') drives a CHOP-Execute DAT that picks the next clip per mode (sequential / random / shuffle-no-repeat / weighted) and animates the Switch index with a crossfade. Exposes Play / Index / Next / Prev / Crossfade / Bpm / Division / Mode / Seed custom pars on the container; emits a state_out Null CHOP so bind_to_channel can read clip_index/beat. Folder is read inside TD. Missing folder → empty pointable montage instead of error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoContainer COMP name.auto_montage
parent_pathNoWhere to build it./project1
folderYesFolder on the TD machine to scan for clips/stills.
extensionsNoAllow-listed extensions (lower-case, no dot).
max_clipsNoCap clip count.
resolutionNoSwitch TOP output resolution [w,h].
modeNoSequence policy: sequential, random, shuffle (no immediate repeat), weighted (per-clip Weight par).shuffle
clockNoTrigger source: beat/bar (Beat CHOP) or interval (LFO CHOP).bar
bpmNoTempo when clock=beat|bar.
divisionNoAdvance every N beats (beat) or N bars (bar).
interval_sNoSeconds between advances when clock=interval.
crossfadeNoCrossfade seconds (0 = hard cut).
autoplayNoStart in playing state.
seedNoIf set, seeds the RNG (reproducible).
Behavior5/5

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

The description discloses extensive behavioral traits: scanning folder, building specific TOP/CHOP network, exposing custom pars, handling missing folder gracefully (empty montage instead of error). Annotations are consistent and the description adds context beyond the simple flags.

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?

The description is a single paragraph but packs many details. It is front-loaded with the main action ('Point at a folder and build...') and then elaborates. Could be more structured with breaks, but no redundancy.

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?

Given the tool's complexity (14 params, internal node network), the description covers functionality, error handling, output signals, and parameter roles. It is complete for an agent to understand and invoke correctly.

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

Parameters4/5

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

All 14 parameters are described in the schema (100% coverage), but the description adds meaning by explaining how parameters like 'mode', 'clock', 'crossfade' affect the montage behavior. This goes beyond schema definitions, providing operational context.

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 clearly states the tool builds a self-running clip montage from a folder. It provides a step-by-step breakdown of internal node construction, distinguishing it from other creation tools like 'create_video_player' or 'create_audio_reactive' in the sibling list.

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?

The description implies usage by stating 'Point at a folder', but does not explicitly state when to use this tool versus alternatives, nor provide exclusion criteria. It assumes the agent will understand the context from the detailed description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pantani/tdmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server