Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.render.start

Starts processing items in the After Effects render queue, optionally targeting a specific job ID, to begin producing output.

Instructions

Start processing items 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.start"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and discloses almost nothing: it does not say whether rendering is asynchronous or blocking, whether it returns a job handle, whether it fails on an empty queue, or how it interacts with ae.render.cancel. Only the mutation intent is conveyed, and even that is not framed as destructive or irreversible.

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 short sentence with the action front-loaded and no filler. It is efficient, though the brevity reflects under-specification rather than tight editing.

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?

For a render-initiation tool with no annotations, no output schema, and an undocumented parameter, the description is far too thin. An agent cannot tell whether this call is long-running, how to track progress, or whether to pass jobId.

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?

Schema description coverage is 0%, and the description never mentions the single optional jobId parameter. Worse, "items" (plural) suggests it renders the whole queue, leaving it unclear whether jobId narrows processing to one job or is ignored, so the description actively muddies the parameter's meaning.

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 pairs a specific verb ("Start") with a specific resource ("render queue"), so the agent knows this initiates rendering rather than inspecting or cancelling it. It does not explicitly contrast itself with ae.render.queue or ae.render.status, but the action is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Start processing items in the render queue" implies the precondition that items must already be queued, which weakly routes the agent to ae.render.queue first. However, it never states when to use this over ae.render.status or ae.render.cancel, nor what happens if the queue is empty.

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