Skip to main content
Glama

ae_add_mask

Apply a rectangular or elliptical mask to a layer, optionally restricting bounds for partial masking. Animate the mask for wipe reveals.

Instructions

Add a rectangular or elliptical mask to a layer. Bounds are in the layer's own pixel space ([left, top, right, bottom]); omit them to mask the whole layer. Combine with ae_animate_mask for wipe-style reveals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
compNo
layerYes
shapeNorect
boundsNo[left, top, right, bottom] in layer space. Defaults to the whole layer.
featherNo
expansionNoMask expansion (px). Negative shrinks.
modeNoadd
invertedNo
nameNo
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that bounds are in layer space and hints at animation combination, but does not specify effects of parameters like mode, inverted, or if masks can be added to layers with existing masks. Basic transparency is present but not thorough.

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?

Two concise sentences with no redundant wording. The first sentence states purpose, the second adds usage nuance. Front-loaded with key information.

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?

The tool has 9 parameters with substantial complexity (modes, inversion, expansion) and no output schema. The description only touches on bounds and animation combination, leaving many behavioral aspects unexplained. Incomplete for the tool's depth.

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 22%. The description adds some value by explaining bounds format and coordinate system, but other parameters (shape, feather, expansion, mode, inverted, name) are not elaborated. The description does not compensate for the low coverage.

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 adds a rectangular or elliptical mask to a layer, and specifies that bounds are in layer space. This distinguishes it from sibling tools like ae_animate_mask, which animates masks rather than adding them.

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?

Provides clear context: bounds in layer space, omission masks whole layer. Mentions combining with ae_animate_mask for reveals. Lacks explicit guidance on when not to use or alternatives, but context is helpful.

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