Skip to main content
Glama
Sign In
after-effects-mcp-enhanced

after-effects-mcp-enhanced

by ku1x
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

import-footage

Import a local file or image sequence into After Effects, with optional addition to a composition by stable ID.

Instructions

Import a local file or image sequence; optionally add it to a composition by stable ID.

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": "import-footage"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
compIdNo
sequenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so the description must carry full behavioral disclosure. It explains the primary action and optional composition addition, but does not mention side effects, permissions, failure modes, or reversibility.

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?

A single, concise sentence that efficiently communicates the core functionality. No unnecessary words or redundant details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, but the description omits any mention of return value or success/failure indicators. It also does not clarify whether the imported footage can be referenced later via an ID, which is relevant for follow-up operations.

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?

The description adds some meaning to parameters: 'path' is described as a local file or image sequence, and 'compId' relates to a composition. However, it does not fully explain the role of 'sequence' (e.g., how it modifies path interpretation) or the exact effect of compId.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the verb 'import' and the resource 'local file or image sequence'. Also mentions the optional action of adding to a composition, which makes it distinct from sibling tools like render-composition or execute-jsx.

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 use this tool versus alternatives. Lacks any mention of scenarios where import-footage is appropriate or not, nor does it reference sibling tools.

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

Deploy Server

Other Tools