Skip to main content
Glama

ae_addAdjustment

Add an adjustment layer to an After Effects composition, optionally applying named effects, to affect all layers below it.

Instructions

After Effects: add an adjustment layer (optionally with effects by name/matchName) affecting everything below it.

Input Schema

NameRequiredDescriptionDefault
nameNo
effectsNo
durationNo
startTimeNo
compositionNameNoComp name; omit to use the active comp.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare this is a mutation tool but not read-only, destructive, or open-world. The description adds useful behavioral context by noting the adjustment layer affects everything below it and can optionally carry effects, but it does not discuss permissions, side effects, or return behavior.

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?

A single efficient sentence with the core action front-loaded, optional detail following, and no wasted words.

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

Completeness2/5

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

For a mutation tool with five parameters and no output schema, the description is thin. It covers the main action and one parameter's semantics, but leaves the roles of name, duration, startTime, and compositionName largely to an under-described schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20%, so the description needs to compensate. It clarifies that the effects array accepts effect names or matchNames, which is useful, but it says nothing about name, duration, or startTime, leaving most parameters unexplained.

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 verb and resource: 'add an adjustment layer' in After Effects. It also adds scope ('affecting everything below it') and optional effects, making it distinguishable from related effect tools, though it does not explicitly name a sibling.

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?

It mentions that effects can optionally be included by name or matchName, but gives no guidance on when to use this tool versus ae_addEffect, ae_addSolid, or other layer-creation tools. No prerequisites or exclusions are stated.

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