Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.project.save

Saves the active After Effects project, optionally to a specified path, so you can persist edits and avoid losing work.

Instructions

Save the currently 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.save"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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 does not disclose whether existing files are overwritten, whether the save is to the original location or to a supplied path, whether errors occur when no project is active, or whether unsaved changes are flushed. For a mutating filesystem-affecting operation this is a substantial gap.

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?

A single front-loaded sentence with no filler, appropriately sized for a simple tool. Its brevity is efficient, though it edges into under-specification rather than being genuinely complete.

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 one-parameter mutation tool with no annotations and no output schema, the description should at minimum explain the path parameter, the save-vs-save-as behavior, and failure modes such as no active project. None of these are covered, so an agent cannot call it confidently.

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?

The single parameter (path) has 0% schema description coverage, and the description never mentions it. It is unclear whether supplying path performs a save-as, creates directories, or overwrites an existing file, so the description adds essentially no meaning beyond the bare schema type.

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?

"Save the currently active After Effects project" gives a specific verb (save) and resource (active project), and the word "currently" distinguishes it from ae.project.open/create/close. It does not clarify whether this is an in-place save or a save-as, which matters given the optional path parameter.

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 explicit guidance on when to call this versus saving through another path, no prerequisite that a project must already be open, and no mention of what happens if no project is active. The only hint is the phrase "currently active," leaving the agent to infer preconditions.

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