Import multiple files into an After Effects project at once, with options to place them in a chosen folder or combine numbered images into a sequence.
Import multiple files into the After Effects project at once
| Name | Required | Description | Default |
|---|---|---|---|
| file_paths | Yes | List of absolute file paths to import | |
| destination_folder | No | Project panel folder to import into (null = root) | |
| import_as_sequence | No | Import numbered image files as a sequence |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the full burden of behavioral disclosure. It only restates the core import action and does not mention side effects, assumptions, failure behavior, or what happens to existing project items. For a mutating operation this leaves significant behavioral context undisclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one short sentence with no wasted words and front-loads the key purpose. It is concise, though it sacrifices useful usage context that could have been added without much bloat.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With a fully described schema and no output schema, the basic call can be constructed. However, the description lacks guidance on how this relates to the singular ae_import_file, what happens when sequence import is enabled, and what the expected result of a batch import is. It is adequate but not complete for a tool with no annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already fully documents all three parameters. The description adds no extra meaning about file_paths, destination_folder, or import_as_sequence, but the baseline of 3 applies because the structured schema carries the parameter documentation burden.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Import'), a clear resource ('After Effects project'), and a clear scope ('multiple files at once'). It distinguishes this tool from the sibling ae_import_file, which handles a single file, without needing to open the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this is for batch imports and implicitly contrasts with the singular ae_import_file, but it never explicitly states when to use this tool versus that alternative. No exclusions or conditions are provided, so the agent must infer the routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.