Skip to main content
Glama
Sign In
AE MCP Server

AE MCP Server

by p10q
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

reorder_layers

Change layer order in After Effects compositions by specifying current and new positions to organize visual elements.

Instructions

Change the order of layers in a composition

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": {
      "compId": "<compId>",
      "layerIndex": "<layerIndex>",
      "newIndex": "<newIndex>"
    },
    "name": "reorder_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault
compIdYesID of the composition
layerIndexYesCurrent index of the layer to move (1-based)
newIndexYesNew index position for the layer (must be between 1 and the total number of layers in the composition)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Change the order' implies a mutation operation, it doesn't specify whether this requires specific permissions, whether the change is immediate or reversible, what happens to other layers' indices, or potential side effects. For a mutation tool with zero annotation coverage, this is inadequate.

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?

The description is a single, efficient sentence that directly states the tool's purpose without any fluff or redundancy. It's front-loaded with the core action and resource, making it immediately understandable. Every word earns its place.

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?

Given that this is a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns (e.g., success/failure, updated layer list), potential errors, or behavioral nuances like how indices are handled after reordering. For a tool that modifies data, more context is needed.

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 the schema already documents all three parameters (compId, layerIndex, newIndex) with clear descriptions. The description adds no additional parameter information beyond what's in the schema, such as format examples or edge cases. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the action ('Change the order') and resource ('layers in a composition'), making the purpose immediately understandable. It distinguishes from siblings like 'delete_layer' or 'modify_layer_properties' by focusing specifically on reordering. However, it doesn't specify whether this affects z-index, timeline order, or another type of ordering, which prevents a perfect score.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'modify_layer_properties' or 'batch_modify_layer_properties' that might handle similar operations, there's no indication of when reorder_layers is the appropriate choice. No prerequisites, constraints, or comparison to other tools are mentioned.

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