Skip to main content
Glama

Create keyframe animation

create_keyframe_animation

Create keyframe-based parameter animations synced to the timeline, with linear or smooth interpolation and optional looping for choreographed motion.

Instructions

Animate parameters along a keyframed curve synced to the timeline — structured motion beyond animate_parameter's LFO (use animate_parameter instead for continuous LFO oscillation). Give time/value keyframes and the targets; this creates a baseCOMP 'keyframe_anim' under parent_path containing an Execute DAT that interpolates the curve each frame (linear or smooth easing) and writes the value onto every target parameter, looping over the keyframe span (or holding the last value). Use it for choreographed moves (a build-up, a drop, a sweep). Returns a summary plus a JSON block with the container path, the Execute DAT (hook) path, the loop duration, the targets, and warnings (including any targets that did not resolve). Returns a friendly error if the keyframes do not span a positive duration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loopNoLoop the animation; otherwise it holds the last value.
easingNoInterpolation between keys: linear, or smooth (eased) for organic motion.smooth
targetsYesParameters to animate, each written as 'nodePath.parName'.
keyframesYesKeyframes (time + value); the curve interpolates between them in order.
parent_pathNoParent network where the keyframe-animation container (a baseCOMP) is created (default '/project1')./project1
Behavior5/5

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

The description discloses creation of a baseCOMP under parent_path, an Execute DAT that interpolates each frame, writing to target parameters, loop/hold behavior, return summary/JSON block, and error handling for non-positive duration. This goes well beyond the annotation hints (readOnly=false, destructive=false) and provides rich behavioral context.

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 yet complete, front-loading the core purpose, then mechanics, use case, return format, and error condition. Every sentence earns its place without 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?

With no output schema, the description explicitly details the return value (summary plus JSON block with container path, hook path, loop duration, targets, warnings) and error behavior. Combined with a fully documented schema and annotations, this is a complete and self-sufficient definition for the tool's complexity.

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?

The input schema covers all 5 parameters with descriptions (100% coverage), so the baseline is 3. The description reinforces relationships (keyframes are time/value, targets are nodePath.parName) but does not add new meaning beyond the schema.

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 animates parameters along a keyframed curve synced to the timeline, explicitly distinguishing it from animate_parameter's LFO behavior. It names the resource (keyframed animation, baseCOMP 'keyframe_anim') and the action (animate parameters).

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?

It explicitly advises using animate_parameter for continuous LFO oscillation and this tool for choreographed moves (build-up, drop, sweep). This gives clear when-to-use and when-not-to-use guidance relative to a sibling tool.

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/lucasmaher-hash/touch-designer-mcp'

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