Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.composition.delete

Deletes a composition from the After Effects project using its composition ID, with confirmation required via an approval token to prevent accidental removal.

Instructions

Delete a composition from the project. 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.composition.delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
approvalTokenNo
compositionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses the confirmation-token requirement, which is useful, but omits critical details for a destructive operation: whether deletion is reversible, what happens to contained layers or animations, permission requirements beyond the token, and error behavior.

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, front-loaded sentences with no wasted wording. The action is stated first and the token requirement second, though 'from the project' is slightly redundant.

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?

For a destructive tool with no annotations, no output schema, and three parameters at 0% schema coverage, the description is too sparse. It does not clarify parameter usage, deletion effects, or safety implications beyond the token requirement.

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 0%, so the description must compensate. It explains the approvalToken's role in confirmation, but leaves 'name' and 'compositionId' completely undocumented, and with zero required parameters it is unclear which identifier is actually needed to target a composition.

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 composition from the project'), clearly distinguishing it from sibling operations like create, inspect, and update. It does not explicitly name an alternative, but the delete verb makes the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The sentence 'Requires confirmation approvalToken' implies a prerequisite for use, but there is no explicit when-to-use guidance, no mention of alternatives, and no clarification of when deletion should be avoided. Usage is only indirectly inferable.

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