Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.render.status

Check the status of render queue jobs in After Effects, optionally by job ID, to monitor completion and identify stalled renders.

Instructions

Check status of jobs in the render queue.

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.render.status"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdNo

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 behavioral burden. It implies a safe read but never says so, and it omits whether omitting jobId returns all jobs, whether results include progress percentages or error states, and whether polling is expected. These are meaningful gaps for a status-checking tool with no structured metadata to lean on.

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, which is structurally sound. However, the brevity comes at the cost of under-specification rather than deliberate economy.

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 an undocumented optional parameter, the definition does not give an agent enough to invoke the tool confidently. It should at minimum explain the jobId-omitted behavior and the shape of the status information returned.

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?

The single parameter jobId has 0% schema description coverage and is never mentioned in the description. The most important behavioral question — whether jobId is optional and what the tool returns when it is omitted — is left entirely undocumented, so the description adds no meaning beyond the bare schema.

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 gives a specific verb and resource: 'Check status of jobs in the render queue.' This clearly identifies a read-only inspection of render jobs. It stops short of distinguishing itself from close siblings such as ae.render.queue or ae.render.cancel, so an agent must infer the boundary between querying status and inspecting the queue.

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 call this versus ae.render.queue, ae.system.status, or the start/cancel tools. It does not state whether this is meant for polling progress, for a one-off check, or what the relationship is to the queue-listing tool.

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