Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.project.open

Opens an existing Adobe After Effects (.aep) project by file path to load its compositions and assets for automation.

Instructions

Open an existing Adobe After Effects project (.aep).

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": {
      "path": "<path>"
    },
    "name": "ae.project.open"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It states the file type but omits what opening does to any currently open project, whether unsaved changes are affected, required permissions/state, and error behavior for missing or invalid files.

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 definition is a single front-loaded sentence with no redundant wording. Its brevity fits a simple one-parameter tool, though the missing details are captured under other dimensions rather than conciseness.

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 low-complexity one-parameter tool this covers the basic action, but opening a project is state-changing and the definition does not explain side effects on the current project, unsaved work, or error cases. With no annotations or output schema, those omissions leave an agent without important operational context.

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?

There is one required 'path' parameter with 0% schema description coverage. The description adds that the path refers to an existing .aep project, which is useful, but it does not clarify path format (absolute/relative), accessibility requirements, or failure behavior.

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?

The description gives a specific verb ('Open') and resource ('Adobe After Effects project') and scopes it to existing .aep files. It is clear enough to separate from create/close, though it does not explicitly name sibling tools or contrast with inspect/validate.

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 word 'existing' implies this is for already-created .aep files and not for new projects, which gives minimal routing against ae.project.create. However, there is no explicit when-to-use guidance, no prerequisites, and no statement about alternatives such as inspect or validate.

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