Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.project.close

Closes the active After Effects project, with an option to save changes before closing.

Instructions

Close the active After Effects project.

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.project.close"
  }
}

Input Schema

NameRequiredDescriptionDefault
saveChangesNo
approvalTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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 and does not meet it. It never states what happens to unsaved changes when saveChanges is false (data loss risk), whether the operation is reversible, or that an approvalToken may be required for a destructive action — all critical for a close operation.

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?

A single short sentence with no filler, so it is concise, but concision here comes at the cost of substance: there is no structure or front-loaded detail beyond the bare purpose.

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, zero-annotation tool with two undocumented parameters and no output schema, the description is far too thin. An agent cannot tell from this whether calling it risks losing work or triggers an approval flow.

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

Parameters1/5

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

Schema description coverage is 0% for two parameters, and the description adds no meaning to either. The saveChanges flag and its default of false — the single most consequential detail about this tool — is never explained, nor is approvalToken's role or how to obtain one.

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 (close) and resource (the active After Effects project), making it distinguishable from siblings like ae.project.save and ae.project.open. It does not explicitly name alternatives, and 'active' is left slightly under-defined (active in what sense — the foreground document?).

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 when-to-use or when-not-to-use guidance: nothing says whether to call ae.project.save first, whether this fails when no project is open, or how it relates to ae.project.create/open. Usage must be inferred entirely from the verb.

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