Skip to main content
Glama

Create video player

create_video_player

Build a movie or clip player with live play, speed, and clip controls. Supports single file or playlist playback via Switch TOP, output as Null TOP.

Instructions

Build a movie/clip player inside a new 'video_player' container under parent_path: one Movie File In TOP, or a playlist of clips fed through a Switch TOP with a Clip selector. Exposes live Play / Speed (and Clip) controls, output as a Null TOP. Pass file paths, or none to get an empty player you point at a file in TD. Use create_video_synth instead when you want a procedurally generated (oscillator/CRT) image rather than playing a video file. Returns the created clip paths, the output Null path, and whether a playlist was built. For VJ clip playback — mix it with create_layer_mixer or make it react with bind_to_channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesNoMovie file path(s). 0 = an empty player you can point at a file later; 1 = a single clip; 2+ = a playlist with a Switch TOP and a Clip selector.
expose_controlsNoExpose live Play / Speed (and Clip, for a playlist) controls.
parent_pathNoParent COMP path the self-contained 'video_player' container is created inside./project1
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true. The description adds that it creates a container, exposes live controls, and returns paths. It does not mention potential overwrite behavior, but given openWorldHint, this is acceptable. Adds value beyond annotations.

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 of ~120 words, packing essential information. It front-loads the purpose and uses concise language. Slightly verbose in listing specific operators (Switch TOP, Clip selector), but still efficient.

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?

Given no output schema, the description adequately explains return values (clip paths, output Null path, playlist flag). It covers constraints (file paths) and suggests integrations. For a tool with 3 parameters and moderate complexity, this is sufficient for an agent to use correctly.

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?

Schema coverage is 100% with good parameter descriptions. The description adds significant meaning: explains behavior based on the number of files (0 = empty player, 1 = single clip, 2+ = playlist with Switch and Clip selector). Also clarifies the effect of expose_controls. Greatly aids understanding.

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 movie/clip player in a 'video_player' container. It specifies input types (file paths) and output (returned paths, Null TOP). It distinguishes from sibling create_video_synth by contrasting video file playback vs procedural generation.

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?

Explicitly states when to use (play video files) and when not (procedural generation, use create_video_synth instead). Also suggests integration with create_layer_mixer or bind_to_channel for VJ clip playback, providing clear context and alternatives.

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