Skip to main content
Glama
After Effects MCP Server

After Effects MCP Server

ae.render.cancel

Stops or pauses an active After Effects render job by ID, letting you halt unwanted rendering and free up resources.

Instructions

Pause or cancel active rendering.

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

Input Schema

NameRequiredDescriptionDefault
jobIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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 burden. It does not say whether cancel discards already-rendered frames, whether pause is resumable, whether the operation is reversible, or what permissions are required — all critical for a destructive-sounding render operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no wasted words and the action front-loaded, but the brevity comes at the cost of under-specification rather than being genuinely tight.

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 state-mutating render-control tool with no annotations, no output schema, and an undocumented parameter, the description leaves too much unresolved. An agent cannot reliably call this without guessing at jobId semantics and the pause/cancel distinction.

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 single jobId parameter is never mentioned. The description fails to say whether jobId is optional, what omitting it does (cancel everything?), or how the same parameter yields pause versus cancel.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb-plus-resource ('Pause or cancel active rendering'), but conflates two distinct operations in one tool without explaining how they differ or how the caller selects between them. It never mentions the jobId parameter, so the agent cannot tell whether the operation targets a single job or all active renders.

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?

No guidance on when to use this versus ae.render.start, ae.render.queue, or ae.render.status. There is no indication of prerequisites (must a render be in flight?) or of what happens if nothing is rendering.

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