Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.layer.delete

Delete a layer from an After Effects composition by name or index; an approval token is required to confirm the destructive action.

Instructions

Delete a layer from a composition. Requires confirmation approvalToken.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ae.layer.delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerNameNo
layerIndexNo
approvalTokenNo
compositionIdNo
compositionNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose two important facts: this is a destructive removal and it gates on an approvalToken, which tells the agent a confirmation step is mandatory. It does not say whether the deletion is reversible, what happens to layer indices of remaining layers, or whether it requires the composition to be open.

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?

Two short sentences with no filler, and the destructive action is front-loaded. The brevity is efficient, though it edges toward under-specification rather than tightness.

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?

A five-parameter destructive tool with no annotations, no output schema, and 0% schema coverage needs far more than two sentences. The agent is left guessing how to identify the target layer and composition and what a successful or failed deletion looks like.

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

Parameters5/5

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

Schema description coverage is 0% and the description explains none of the five parameters except approvalToken, and even that only in terms of the requirement rather than its format or provenance. It is silent on the critical ambiguity of layerName versus layerIndex and compositionId versus compositionName, and on which combination is actually needed despite zero required fields.

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?

States a specific verb and resource ('Delete a layer from a composition'), which is enough for an agent to identify the operation. It does not explicitly separate itself from nearby siblings such as ae.composition.delete or ae.layer.duplicate, leaving the scope distinction (single layer vs whole composition) implicit.

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?

The only guidance is 'Requires confirmation approvalToken,' which is a prerequisite rather than a when-to-use rule. There is no statement of when to delete versus removing/duplicating a layer, no mention of preconditions like the layer being selected or unlocked, and no exclusion of the sibling delete tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.