Skip to main content
Glama

animate-from-data

Turn any numeric data series into After Effects keyframes. Maps raw values to property ranges automatically for clean animation.

Instructions

Generate After Effects keyframes for a layer property directly from an arbitrary numeric data series - stock prices, sensor readings, scores, survey results, or any other time-ordered numbers (not audio; see animate-to-audio for that). Provide either data (explicit {time, value} points) or values + interval (an evenly-spaced series with an implied time step) - not both. Each raw value is normalized using [inputMin, inputMax] (auto-detected from the series when not given, so an unknown-range series still maps cleanly) and mapped to [outputMin, outputMax], with the same optional response curve and smoothing animate-to-audio uses. Targets a plain layer property (e.g. 'ADBE Opacity') by default, or an effect's property when effectIndex/effectName/effectMatchName is given.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoExplicit {time, value} points, in seconds and raw data units (max 2000, one point becomes one keyframe). Does not need to be pre-sorted by time. Provide this or values+interval, not both.
curveNoResponse shaping (default: linear). 'exponential' emphasizes high values; 'logarithmic' boosts low-value detail.
valuesNoRaw values for an evenly-spaced series (one every `interval` seconds, starting at `startTime`; max 2000). Provide this with interval, or use `data` instead for explicit per-point times.
compNameNoName of the target composition. Preferred over compIndex when both are given.
inputMaxNoRaw data value mapped to outputMax. Auto-detected from the series (after smoothing) when omitted.
inputMinNoRaw data value mapped to outputMin. Auto-detected from the series (after smoothing) when omitted.
intervalNoSeconds between consecutive `values` entries. Required when `values` is given.
compIndexNo1-based composition index, used if compName is not given.
layerNameNoName of the target layer (alternative to layerIndex).
outputMaxYesProperty value at inputMax (or the series' highest point, when inputMax is not given).
outputMinYesProperty value at inputMin (or the series' lowest point, when inputMin is not given).
startTimeNoSeconds to offset every generated keyframe by. In `values` mode this is also where the series starts (default: 0).
effectNameNoDisplay name of the effect to target.
layerIndexNo1-based index of the target layer within the composition.
effectIndexNo1-based index of the effect in the layer's Effects group, to target an effect property instead of a plain layer property.
propertyNameNoTarget property name or matchName (e.g. 'ADBE Opacity', 'ADBE Scale', 'ADBE Rotate Z' - matchNames are locale-independent and preferred). Used when propertyPath is not given, or as the effect-property fallback.
propertyPathNoPath to the target property, from the effect root (if an effect selector is given) or from the layer root otherwise, e.g. ['Compositing Options', 'Effect Opacity'] or [3, 1].
clearExistingNoRemove the property's existing keyframes first (default: true).
propertyIndexNoFallback target property index under the effect root (effect targeting only).
effectMatchNameNoInternal matchName of the effect to target.
keyframeOptionsNoOptional graph/easing controls applied uniformly to every keyframe this call generates.
smoothingWindowNoMoving-average window (in samples) applied to raw values before mapping, to smooth out noisy data (default: 1 = no smoothing).
Behavior4/5

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

With no annotations, the description carries the full burden. It explains key behavioral aspects like normalization with auto-detected input range, mapping to output range, response curve, and smoothing. However, it omits the default destructive behavior of clearing existing keyframes (clearExisting defaults to true in the schema), which is a significant side effect not disclosed in the description.

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 well-structured and front-loaded, starting with the core purpose and then progressively adding necessary detail. It is concise for the complexity, covering input modes, normalization, and targeting in a few sentences without unnecessary fluff, earning its length.

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 the tool has 22 parameters with comprehensive schema descriptions, the description provides a solid high-level overview that ties concepts together. It covers the main usage patterns and normalization logic, but could mention default behaviors like clearExisting and the max 2000 points limit (though that is in the schema). Overall, it is adequate for a complex tool with rich schema support.

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%, so baseline is 3. The description adds significant meaning by explaining the normalization logic that ties inputMin/inputMax to outputMin/outputMax, and clarifies the relationship between data vs values+interval modes. It also introduces the concept of targeting effect properties, enriching the schema's existing parameter 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 it 'Generate After Effects keyframes for a layer property directly from an arbitrary numeric data series', specifying the action, resource, and input type. It also distinguishes itself from the sibling tool animate-to-audio by explicitly stating 'not audio; see animate-to-audio for that', providing clear differentiation.

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 provides explicit usage guidance by contrasting with animate-to-audio and explaining the two mutually exclusive input modes (data vs values+interval). It also clarifies when to target effect properties versus plain layer properties, offering clear when-to-use and when-not-to-use instructions.

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/a-y-ibrahim/after-effects-mcp'

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