Skip to main content
Glama
Sign In
mcp-ae

mcp-ae

by shibin0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ae_create_folder

Create a folder in the After Effects project panel to organize assets, optionally nesting it within a parent folder.

Instructions

Create a folder in the After Effects project panel

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

Input Schema

NameRequiredDescriptionDefault
nameYesFolder name
parent_folderNoParent folder name (null = project root)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose side effects itself. It confirms a mutating 'create' action, but does not say whether an open project is required, what happens if a folder with the same name exists, or what the function returns. It adds only the project-panel context, leaving key behavioral details to inference.

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?

Single sentence, no filler, with the essential verb-resource-location structure front-loaded. Every word contributes to meaning.

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?

For a simple two-parameter creation tool, the schema covers parameter semantics well, but the description omits operational prerequisites such as needing an open project and error behavior for duplicate names or invalid parents. Without annotations or an output schema, an agent still has to infer some execution context.

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%, and both parameters already contain clear descriptions in the schema. The tool description adds no extra semantic detail about the name or parent_folder parameters, so it meets the baseline but nothing more.

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 states a specific verb ('Create'), a specific resource ('folder'), and a specific location ('After Effects project panel'), cleanly distinguishing this from sibling layer/composition/project-item tools. No other sibling creates folders, so there is no ambiguity.

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 gives no guidance about when to choose this tool over alternatives, nor any prerequisites or exclusions. It does not mention that a project must be open or how this relates to folder organization workflows. This is essentially a statement of function, not usage context.

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