AE MCP Server

Overview Schema Source Related Servers Discussions Admin

execute_script

Run custom ExtendScript code in Adobe After Effects to automate tasks, modify projects, or control application functions programmatically.

Instructions

Execute a custom ExtendScript in After Effects

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": {
      "script": "<script>"
    },
    "name": "execute_script"
  }
}

Input Schema

Name	Required	Description	Default
`script`	Yes	The ExtendScript code to execute
`wrapInTransaction`	No	Wrap script in app.beginUndoGroup/endUndoGroup
`undoGroupName`	No	Name for the undo group	Script Execution

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 26, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('execute') but doesn't mention critical behaviors like whether this is a read-only or destructive operation, potential side effects (e.g., modifying project state), error handling, or performance implications (e.g., script execution time). This is inadequate for a tool that runs arbitrary code.

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 description is a single, clear sentence with zero wasted words. It's front-loaded with the core action and context, making it easy to parse quickly. Every word earns its place by conveying essential information efficiently.

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?

Given the complexity of executing arbitrary code in After Effects, no annotations, and no output schema, the description is insufficient. It lacks details on safety (e.g., is this destructive?), expected outputs, error conditions, or integration with sibling tools. This leaves significant gaps for an agent to use the tool effectively.

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?

Schema description coverage is 100%, so the schema fully documents all three parameters. The description adds no additional meaning beyond what's in the schema (e.g., it doesn't explain ExtendScript syntax or provide examples). This meets the baseline for high schema coverage but doesn't enhance understanding.

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 clearly states the verb ('execute') and resource ('custom ExtendScript in After Effects'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'batch_execute' or specify that this is for arbitrary code execution versus predefined operations, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an open project), compare it to sibling tools like 'batch_execute' or 'set_expression', or specify use cases for custom scripting versus built-in tools, leaving the agent with minimal context for selection.

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

Deploy Server