Skip to main content
Glama

Create keyframe animation

create_keyframe_animation

Animate parameters along a keyframed curve synced to the timeline for structured motion beyond continuous LFO oscillation. Provide time/value keyframes and target parameters; the tool creates an interpolated animation that loops or holds.

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

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

Annotations indicate readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description discloses that the tool creates a baseCOMP container with an Execute DAT that writes target parameter values each frame, loops, and returns warnings/errors. It does not contradict annotations and adds context about the creation and behavior.

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 that front-loads the purpose and differentiator, then details behavior and output. It is concise without unnecessary information, though could be slightly more structured.

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 (5 parameters, nested keyframes, no output schema), the description comprehensively covers input requirements, creation process, interpolation types, looping, return format, and error handling. It leaves no critical gaps.

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 description coverage is 100%, but the description adds operational detail beyond the schema: it explains that keyframes create an interpolated curve, how looping works, and what the output contains. This adds value for the agent despite thorough schema descriptions.

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 using keyframes on a timeline, distinguishing it from animate_parameter's LFO oscillation. It specifies the verb 'animate' and the resource 'parameters along a keyframed curve', and explicitly contrasts with the sibling tool.

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 provides clear guidance on when to use this tool (choreographed moves like build-up, drop, sweep) and explicitly advises using animate_parameter instead for continuous LFO oscillation. It does not mention other exclusions, but the context is 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