Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.project.create

Create a new Adobe After Effects project and optionally close existing projects first, providing a clean workspace for composition and automation tasks.

Instructions

Create a new Adobe 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.create"
  }
}

Input Schema

NameRequiredDescriptionDefault
closeExistingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/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 and discloses nothing beyond the bare action. Critically, it never mentions that the sole parameter (closeExisting, defaulting to true) implies the current project may be closed, which is a potential data-loss consequence an agent must know before calling.

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 single sentence is clean and front-loaded with no filler, but its brevity comes at the cost of under-specification rather than efficiency. It reads as a title restatement rather than a useful definition.

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 state-changing project-level operation with no annotations, no output schema, and an undocumented parameter whose default closes existing work, the definition is far too thin. An agent lacks what it needs to call this safely.

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?

Only one optional parameter exists and schema description coverage is 0%, so the description could have explained closeExisting's effect and default. It says nothing about it, leaving the default-to-true, close-the-existing-project behavior entirely undocumented in prose.

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 ('Create') and resource ('a new Adobe After Effects project'), so the action is unambiguous. The word 'new' implicitly contrasts with the sibling ae.project.open, but the description never makes that distinction explicit.

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 guidance on when to create versus when to open an existing project, and no mention of prerequisites such as having After Effects running or a project already loaded. The agent must infer the create/open split from tool names alone.

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