Track progress of background After Effects renders started in this session. Omit the job ID to list all jobs, or pass one to check a specific render's status.
Progress of background renders started by start-render (or run-script startRender) from this session.
| Name | Required | Description | Default |
|---|---|---|---|
| jobId | No | Job id; omit to list all jobs |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It usefully discloses the session-scoping constraint (only jobs from this session are visible), but says nothing about return shape, whether jobs persist after completion, or whether polling is expected for a tool whose whole purpose is progress tracking.
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?
A single front-loaded sentence that establishes the resource and its scoping constraint with no filler; the parenthetical naming the alternative entry point is worth its space.
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?
For a simple one-optional-param read with full schema coverage and no output schema, the core is covered, but the agent is left guessing what 'progress' looks like in the response and whether completed jobs remain queryable.
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 at 100% schema coverage, with the schema already stating 'omit to list all jobs'. The description adds no further detail on jobId format or listing behavior, so the baseline 3 applies.
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?
Names a specific resource (background render progress) and pins it to jobs started by start-render / run-script startRender in this session, which separates it from render-frame and start-render. It lacks an explicit verb ('retrieve/report'), but the scope is unambiguous.
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 reference to start-render and run-script startRender implies the follow-up role this tool plays after launching a job, and 'from this session' implies a boundary. There is no explicit statement of when not to use it (e.g. completed/older jobs) or what to do instead.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.