Skip to main content
Glama
Sign In
mcp-ae

mcp-ae

by shibin0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ae_precompose_layers

Combine multiple layers into a new nested composition to simplify After Effects projects. Specify the source composition, layer names, and new comp name to precompose with selected attributes.

Instructions

Precompose a set of layers into a new nested composition

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "comp_name": "<comp_name>",
      "layer_names": "<layer_names>",
      "new_comp_name": "<new_comp_name>"
    },
    "name": "ae_precompose_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault
comp_nameYesSource composition name
layer_namesYesNames of layers to precompose
new_comp_nameYesName for the new precomposition
move_all_attributesNoMove all attributes into new comp (true) or keep in parent (false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the high-level action. It does not mention that precomposing typically modifies the source composition, replaces the selected layers with the new nested comp, or how attributes are affected, leaving an AI agent unaware of important side effects.

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?

The description is a single, well-formed sentence with no filler or redundant detail. The key verb and object are front-loaded, and every word contributes to the meaning.

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 basic call is inferable from the schema and the one-line description, but the tool has no output schema and no annotations. Important context about side effects, return value, and behavioral constraints is missing, so the description is only minimally viable rather than fully complete.

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

Parameters3/5

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

Schema coverage is 100%, so the parameters are already documented. The description adds minimal semantic value beyond the schema, though 'new nested composition' loosely maps to new_comp_name and 'set of layers' maps to layer_names.

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 uses a specific verb ('Precompose') with a clear resource ('a set of layers') and outcome ('a new nested composition'). This uniquely identifies the operation among the large sibling list, and the result is concrete enough for an agent to know what will happen.

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 guidance about when to use this tool versus alternatives such as ae_create_composition, nor any prerequisites, exclusions, or fallback conditions. The intended usage must be inferred entirely from the verb, so the description does not actively route the agent.

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