Skip to main content
Glama

add_text_layer_advanced

Add a text layer to an After Effects composition with advanced styling options including font, color, tracking, leading, stroke, and justification.

Instructions

Add a text layer with advanced styling options

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
textYesText content
colorNo
compIdNo
leadingNoLine height
compNameNo
fontSizeNo
positionNo
trackingNoLetter spacing
fontFamilyNo
strokeColorNo
strokeWidthNo
baselineShiftNo
justificationNo
strokeOverFillNo
Behavior2/5

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

No annotations are provided, so the description should fully disclose behavioral traits. It only mentions 'advanced styling options' without specifying what behaviors are involved (e.g., whether it creates a new layer, what default values are used, or how nested objects like color and position are interpreted). The description leaves significant behavioral ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short—one sentence. It is not verbose, but it lacks necessary detail. It earns a middle score because it is not bloated, but the brevity sacrifices usefulness.

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?

With 15 parameters (including nested objects), no output schema, and no annotations, the description is insufficient. It does not explain what the tool returns, the meaning of 'advanced' styling options, or the relationship to other layer tools. The description is incomplete for effective tool selection and invocation.

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 low at 20%. The description adds no parameter-level information beyond what the schema already provides. With 15 parameters including complex nested objects (color, position), the description fails to explain their structure or role, leaving agents to guess.

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

Purpose3/5

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

The description states 'Add a text layer with advanced styling options', which is a clear verb+resource pair. However, it does not differentiate from its sibling 'add_text_layer', leaving ambiguity about what 'advanced' means exactly. This is a minimum viable description.

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 usage guidelines are provided. The description does not indicate when to use this tool versus the simpler 'add_text_layer' sibling, nor does it mention any prerequisites or context for using advanced styling options.

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/davidcasan/MCP-AE2'

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