Skip to main content
Glama

Record movie / sequence

record_movie

Record a TouchDesigner TOP to a .mov or .mp4 movie file for exporting clips or loops. Start recording with file path and FPS; optionally auto-stop after a set duration or stop manually.

Instructions

Record a TOP to a movie file (.mov/.mp4) via a Movie File Out TOP — for exporting a clip or a loop, where render_output only saves a single frame. start begins recording (pass file, fps); pass seconds to auto-stop after a fixed length, or call stop to finish (stop also cleans up the recorder node). The file is written by TouchDesigner on the TD machine. For individual numbered frames, use render_output per frame.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNostart recording the TOP to a file, or stop the current recording.start
node_pathYesPath of the TOP to record.
fileNo(start) Output movie path on the TD machine, with a .mov or .mp4 extension. Absolute path recommended.
fpsNo(start) Frames per second.
secondsNo(start) If set, auto-stop after this many seconds (records a fixed-length loop); otherwise record until you call stop.
Behavior4/5

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

Annotations already indicate non-read-only and non-destructive. The description adds valuable context: stop cleans up the recorder node, file is written on the TD machine (path locality), and auto-stop behavior via seconds. This provides practical behavioral details 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (three sentences), front-loaded with the main purpose, and every sentence adds value. No unnecessary words or repetition.

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 5 parameters, no output schema, and existing annotations, the description covers the full recording lifecycle (start/stop/auto-stop), differentiates from sibling, and notes file location on TD machine. It is sufficient for correct agent invocation, though it could mention overwrite behavior or error states for completeness.

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?

Schema coverage is 100% with descriptions, so baseline is 3. The description enriches parameter meaning: it explains action start/stop context, recommends absolute path for file, mentions fps default, and clarifies seconds for auto-stop. This adds semantics beyond the schema definitions.

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 records a TOP to a movie file via Movie File Out TOP, and explicitly contrasts with render_output (single frame). The verb 'record' and resource 'TOP to movie file' are specific, and the mention of .mov/.mp4 extentsions adds clarity.

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?

The description explains when to use this tool (exporting clips/loops) and contrasts it with render_output (single frames). It also provides usage flow: start with file and fps, optional seconds for auto-stop, then stop to finish. It could be more explicit about not using for single frames, but the guidance is clear and sufficient.

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