Skip to main content
Glama

ae_set_blend_mode

Set a layer's blending mode in After Effects, choosing from normal, multiply, screen, overlay, and more to control composite interactions.

Instructions

Set a layer's blending mode (normal, multiply, screen, overlay, add, lighten, darken, soft-light, hard-light, color-dodge, color-burn, difference, luminosity).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
compNo
layerYes
modeNonormal
Behavior2/5

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

With no annotations, the description bears full responsibility for disclosing behavioral traits. It fails to mention that the operation modifies an existing layer, potential reversibility, or any side effects. It only lists the mode options without clarifying the nature of the update.

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, concise sentence that immediately states the action and lists options. It is front-loaded and free of fluff, but could benefit from slightly more structure to improve readability.

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?

Given no output schema, no annotations, and multiple siblings, the description is insufficient. It lacks details about required parameters, input formats, return value, and when to use. While the tool is simple, the description does not fully equip an agent to use it correctly in diverse contexts.

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 coverage is 0%, so the description must explain parameters. It adds value for the 'mode' parameter by listing valid values (though using hyphens vs underscores inconsistently), but it provides no explanation for 'comp' or 'layer' (e.g., what they represent, format, or if defaults apply).

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 clearly states 'Set a layer's blending mode', specifying the verb and resource. It lists the allowed modes, distinguishing it from sibling tools that add layers or effects. However, it could be more precise by including 'in a composition' to fully specify the context.

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?

No guidance on when to use this tool versus alternatives (e.g., ae_set_effect_param or other layer modifications). No prerequisites or context provided. The description only states what it does, not when to invoke it.

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/Phanikondru/openshowreel'

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