Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.assets.inspect

Inspect imported media footage items in an After Effects project by name or asset ID to verify source details before editing.

Instructions

Inspect imported media footage items in the project.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
assetIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/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 behavioral burden. 'Inspect' implies a read-only operation, but the description does not disclose whether authentication is required, what is returned, whether it works for missing assets, or how errors are surfaced. This is a significant gap for a tool with no annotation coverage and no output schema.

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?

The single sentence is front-loaded and contains no wasted wording. However, it is arguably too terse for a tool with undocumented parameters, leaving the description under-specified rather than efficiently concise.

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 undocumented parameters, the description is incomplete for the tool's modest complexity. It states what is inspected but omits parameter behavior, return format, and operational constraints.

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

Parameters1/5

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

The schema has two parameters (name and assetId) with 0% description coverage, and the description adds no meaning about their roles, requiredness, or mutual exclusivity. It does not clarify whether either parameter can be omitted, whether both can be supplied, or how they are interpreted.

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 uses a specific verb ('Inspect') and resource ('imported media footage items in the project'), clearly distinguishing it from the import sibling. It does not explicitly differentiate itself from other inspect tools such as ae.composition.inspect or ae.layer.inspect, but the resource is narrow enough to be clear.

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 explicit guidance on when to use this tool versus alternatives or prerequisites. The phrase 'imported media footage items' implies usage after import, but no conditions or exclusions are stated.

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