Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.project.validate

Validate After Effects project integrity by checking for missing footage and broken references before rendering or sharing.

Instructions

Validate project integrity, checking for missing footage or broken references.

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.validate"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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, and it discloses almost nothing: it does not say whether validation is read-only or mutates the project, whether it blocks, or whether problems are returned as a list or surfaced as an error. For a diagnostic tool, the shape of the failure signal is the most important behavioral fact and it is absent.

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 tight sentence that front-loads the action and immediately qualifies it with the two things checked. No filler, no repetition of the tool name.

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 and no output schema, the description is the only source of information about behavior, yet it omits the return contract (issue list vs. thrown error) and any precondition such as an open project. For a zero-parameter diagnostic that an agent invokes blind, this leaves a real gap.

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 nothing for the description to clarify beyond the schema, which is fully self-describing with an empty properties object. Baseline 4 applies for a parameterless tool.

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+resource pair ('Validate project integrity') and elaborates what validation covers ('missing footage or broken references'), which tells an agent this is a check, not a query or mutation. It does not distinguish itself from the nearby ae.project.inspect, so an agent must guess which one answers project-health questions.

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 run this versus ae.project.inspect or ae.project.open, no prerequisite (does the project need to be open first?), and no statement about what to do with the result. The agent is left to infer the whole calling context.

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