Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.timeline.inspect

Inspect composition timeline hierarchy, layer timing, and parent relationships to understand structure and timing before editing or automating After Effects projects.

Instructions

Inspect composition timeline hierarchy, layer timing, and parent relationships.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ae.timeline.inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
compositionIdNo
compositionNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. 'Inspect' implies a read, but the description never confirms it is non-mutating, says nothing about permissions or errors when the composition is missing, and gives no hint of what the inspection returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, covering the resource and the three things inspected. Appropriately sized, though it omits much that a reader would need.

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?

With no annotations, no output schema, and two completely undocumented optional parameters, the definition leaves the agent guessing on input selection and return shape. For an inspection tool meant to yield hierarchical data, this is under-specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and both compositionId and compositionName are undocumented. The description mentions 'composition' as the scope but never explains whether the two parameters are alternatives, which is required, or what format an ID takes, so it does little to compensate for the schema gap.

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?

States a specific verb and resource ('Inspect composition timeline hierarchy') and enumerates the content returned: layer timing and parent relationships. This distinguishes it reasonably from ae.composition.inspect and ae.layer.inspect, which the timeline/relationship framing does not cover.

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?

There is no guidance on when to choose this over ae.composition.inspect or ae.layer.inspect, nor any prerequisites (e.g., must a composition be open or active?). The agent must infer the selection condition from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.