Skip to main content
Glama

ae_applyGradient

Applies a Gradient Ramp with exact hex colors to an After Effects layer, defined by color stops, linear or radial type, and angle. Set direction and scatter to control the gradient.

Instructions

After Effects: apply a reliable gradient (Gradient Ramp) with real colors. stops [{color:hex}, ...] (first + last used), type linear|radial, angleDeg (linear direction).

Input Schema

NameRequiredDescriptionDefault
typeNo
blendNoramp scatter 0-..
layerYesLayer name or 1-based index.
stopsYes
angleDegNo
compositionNameNoComp name; omit to use the active comp.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare that this is a non-read-only, non-destructive, closed-world operation. The description adds useful behavior about stops (first and last used), but it does not explain whether a new effect is added or an existing gradient is replaced, nor what layer targeting behavior to expect.

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 short and front-loaded with the key action and parameters. A few terms such as 'reliable' and 'real colors' are somewhat vague, but overall it avoids waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description gives enough context to identify a gradient application tool but not enough for a fully informed mutation call. It omits explanation of layer targeting, composition behavior, and how blend interacts with the ramp, despite having no output schema to cover those 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 coverage is only 50%, and the description compensates by clarifying the stops format, that only first and last stops are used, the linear|radial type values, and that angleDeg controls linear direction. It leaves blend and layer targeting unexpanded in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific After Effects action: applying a Gradient Ramp gradient. It names the effect and core inputs, making the tool's purpose clear, but it does not explicitly distinguish itself from generic effect tools such as ae_addEffect or ae_setEffectProperties.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this instead of related tools, such as adding a generic effect and configuring it. The intended use is implied only by the mention of Gradient Ramp.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools