Skip to main content
Glama
Sign In
AE MCP Server

AE MCP Server

by p10q
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

add_camera_layer

Add a camera layer to an After Effects composition with configurable lens presets or custom focal length settings.

Instructions

Add a camera layer to 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>"
    },
    "name": "add_camera_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
compIdYesID of the composition
nameNoName of the camera layerCamera
presetNoCamera lens preset50mm
focalLengthNoFocal length in mm (for custom preset)

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?

With no annotations provided, the description carries full burden for behavioral disclosure. 'Add' implies a write/mutation operation, but the description doesn't specify whether this requires specific permissions, if it's reversible, what happens on success/failure, or any rate limits. It lacks critical context for safe and effective use.

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 states the core purpose without any wasted words. It's appropriately sized for a straightforward tool and front-loads the essential information.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after adding the layer (e.g., returns layer ID, success status), doesn't mention potential side effects, and lacks usage context. The 100% schema coverage helps with parameters but doesn't compensate for missing behavioral and output information.

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 fully documents all 4 parameters. The description adds no additional parameter information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 ('Add') and target resource ('a camera layer to a composition'), making the purpose immediately understandable. It distinguishes from siblings like 'add_light_layer' or 'add_null_layer' by specifying the type of layer being added. However, it doesn't explicitly differentiate from all sibling 'add_' tools beyond the layer type.

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. It doesn't mention prerequisites (e.g., needing an existing composition), when not to use it, or what alternatives exist among the many sibling tools for different layer types or operations.

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