Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.assets.import

Import video, image, and audio files into an After Effects project, optionally placing them in a specified folder for organized asset management.

Instructions

Import video, image, or audio media footage into the project.

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": {
      "filePath": "<filePath>"
    },
    "name": "ae.assets.import"
  }
}

Input Schema

NameRequiredDescriptionDefault
filePathYes
folderNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure and falls well short. It does not say whether the file is copied into the project or merely referenced, whether a project must be open first, how duplicates or unsupported formats are handled, or whether the operation is reversible.

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 or redundant wording. It is efficient, though its brevity contributes to the missing usage and parameter context rather than being a virtue on its own.

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?

This is a mutation-style import operation with no annotations, no output schema, and two undocumented parameters, so the description should carry much more weight. It omits prerequisites, side effects, and any indication of what the tool returns (e.g., an asset identifier) that an agent would need to chain subsequent calls.

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 never mentions filePath or folderName. The phrase 'video, image, or audio' implicitly hints at acceptable file types for filePath, but the destination-folder parameter receives no explanation at all, so the schema gaps remain unfilled.

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 pairs the specific verb 'Import' with the resource type ('video, image, or audio media footage') and the destination ('into the project'), so the agent knows exactly what operation is being performed. It does not distinguish itself from the sibling ae.assets.inspect, but the action is unambiguous on its own.

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 guidance on when to use this versus ae.assets.inspect or other asset-related siblings, and no stated prerequisites such as requiring an open project. The sentence only describes what the tool does, leaving the agent to infer the conditions under which it applies.

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