Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Import Ae Comps

import_ae_comps

Import After Effects compositions from a .aep file into a target bin. Specify composition names optionally; the operation fails safely if the file is missing or no items are added.

Instructions

Import After Effects compositions from an .aep file, failing closed when the file does not exist or when the target bin gains no items.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comp_namesNoArray of composition names to import. If omitted, imports all comps.
target_binNoTarget bin name or node ID (optional)
ae_project_pathYesFull path to the .aep file

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.14.4
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Tool-specific result data when ok is true."
+    },
+    "error": {
+      "description": "Failure detail when ok is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the tool completed successfully.",
+      "type": "boolean"
+    },
+    "tool": {
+      "description": "The registered MCP tool name.",
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool"
+  ],
+  "type": "object"
+}
  2. Addedv1.4.0
  3. Removedv1.1.5
  4. First observedv1.1.1

TDQS

A4/5.0
Behavior4/5

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

The description goes beyond annotations by stating 'failing closed' and specifying two exact failure conditions (file does not exist, target bin gains no items). This gives the agent concrete expectations for error behavior on a mutating operation. It does not cover every edge case, but the disclosed behavior is meaningful.

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?

One compact sentence front-loads the primary action and source, then appends the key failure behavior. Every phrase earns its place; there is no redundant restatement of the title or schema.

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

Completeness4/5

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

With an output schema present and full parameter schema coverage, the description covers the most important operational nuance (fail-closed behavior). Minor gaps like dependency on an After Effects connection or behavior when only some comp_names are valid are not addressed, but the overall picture is sufficient for a competent agent.

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 parameter semantics are already fully documented. The description's 'file does not exist' and 'target bin gains no items' phrasing subtly relates to ae_project_path and target_bin, but it does not add new parameter-level meaning beyond the schema.

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?

The description uses a specific verb ('Import') with a precise resource ('After Effects compositions') and source format ('.aep file'), making the tool's purpose immediately clear. This distinguishes it from sibling import tools like import_media, import_folder, and import_sequences by the AE-specific domain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is only implied: an agent can infer this is for bringing Ae comps from an .aep into the project, but there is no explicit when-to-use guidance or comparison to alternatives such as import_sequences or import_media. The sibling list contains many import tools, so explicit routing would add value.

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