Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.project.inspect

Inspect the current After Effects project to view its structure, active items, and compositions, helping you understand project state before making changes.

Instructions

Inspect current project structure, active items, and compositions.

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.project.inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It usefully scopes the operation to the 'current project' (an implicit active-project prerequisite) and implies a non-mutating read, but it does not describe the shape of results or what happens if no project is open.

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?

A single short sentence with the resource front-loaded and no filler. Every word contributes to identifying what is inspected.

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?

There is no output schema, so the description is the only source of information about what comes back, and it lists three vague categories ('structure', 'active items', 'compositions') without detail. Given the tool's simplicity and lack of parameters, this is adequate but leaves the agent guessing about result granularity.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description misrepresents or obscures the parameterless contract.

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?

Uses a specific verb ('Inspect') with a specific resource ('project') and enumerates what is returned: structure, active items, compositions. This clearly separates it from mutation siblings like ae.project.save or ae.project.close, though it does not explicitly differentiate itself from inspection siblings such as ae.composition.inspect or ae.assets.inspect.

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?

The verb 'Inspect' implies a read-only, information-gathering use case, and 'current project' hints at the operating context. However, there is no explicit when-to-use guidance, no statement of prerequisites, and no routing to alternatives like ae.project.validate or ae.composition.inspect when a narrower inspection is wanted.

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