Retrieve an After Effects project overview including file path, dirty flag, bit depth, comps/footage/folders, render queue count, and version; optionally include footage details.
After Effects: project overview — file path, dirty flag, bit depth, every item (comps/footage/folders with ids, sizes, durations, folder), render queue count, AE version.
| Name | Required | Description | Default |
|---|---|---|---|
| includeFootage | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds useful behavioral context by listing what the call returns, including project metadata, all items, render queue count, and AE version. It does not explain the includeFootage parameter or whether large item lists could make the call heavy.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence followed by a compact list of returned fields. It contains no redundant or wasted language.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Because there is no output schema, the description does a good job of enumerating return values. However, the only input parameter is undocumented in both the schema and description, leaving a clear gap in how to control footage inclusion.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There is one optional parameter, includeFootage, with 0% schema description coverage. The description mentions footage items in the return payload but never explains what includeFootage toggles or how it affects the result.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies an After Effects project-state retrieval and enumerates the fields returned, including file path, dirty flag, bit depth, items, render queue count, and AE version. It is specific about the resource but does not explicitly distinguish this from sibling tools like ae_getCompState or pr_getProjectState.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies this is a project overview tool, but it gives no explicit guidance on when to use it instead of alternatives such as ae_getCompState or pr_getProjectState. There are no exclusions, prerequisites, or usage conditions stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.