Skip to main content
Glama

Render After Effects Template

ae_render_template

Render After Effects compositions using aerender command-line tool. Verify commands with dry-run option before executing full render.

Instructions

Invoke aerender to render an AE comp. Use dryRun first to verify command.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathYes
compNameYes
outputPathYes
aerenderBinNo
dryRunNo

Implementation Reference

  • src/tools/ae.ts:99-125 (registration)
    The tool 'ae_render_template' is registered on the MCP server using server.registerTool() with its schema and handler defined inline.
    server.registerTool(
      'ae_render_template',
      {
        title: 'Render After Effects Template',
        description: 'Invoke aerender to render an AE comp. Use dryRun first to verify command.',
        inputSchema: z.object({
          projectPath: z.string(),
          compName: z.string(),
          outputPath: z.string(),
          aerenderBin: z.string().optional(),
          dryRun: z.boolean().default(true)
        })
      },
      async ({ projectPath, compName, outputPath, aerenderBin, dryRun }) => {
        try {
          const bin = aerenderBin || config.aerenderBin;
          if (!bin) return errorResult('AERENDER_BIN is not configured');
          const args = ['-project', safePath(projectPath), '-comp', compName, '-output', safePath(outputPath)];
          if (dryRun) return textResult({ dryRun: true, command: [bin, ...args].join(' ') });
          const result = await runCommand(bin, args);
          if (result.code !== 0) return errorResult('aerender failed', result.stderr);
          return textResult({ ok: true, outputPath, stdout: result.stdout });
        } catch (err) {
          return errorResult('Failed to render AE template', String(err));
        }
      }
    );
  • The handler function for 'ae_render_template'. It resolves the aerender binary, builds CLI args, optionally does a dry run, or executes aerender via runCommand and returns the result.
    async ({ projectPath, compName, outputPath, aerenderBin, dryRun }) => {
      try {
        const bin = aerenderBin || config.aerenderBin;
        if (!bin) return errorResult('AERENDER_BIN is not configured');
        const args = ['-project', safePath(projectPath), '-comp', compName, '-output', safePath(outputPath)];
        if (dryRun) return textResult({ dryRun: true, command: [bin, ...args].join(' ') });
        const result = await runCommand(bin, args);
        if (result.code !== 0) return errorResult('aerender failed', result.stderr);
        return textResult({ ok: true, outputPath, stdout: result.stdout });
      } catch (err) {
        return errorResult('Failed to render AE template', String(err));
      }
    }
  • The input schema for ae_render_template using Zod: projectPath, compName, outputPath, optional aerenderBin, and dryRun (default true).
    'ae_render_template',
    {
      title: 'Render After Effects Template',
      description: 'Invoke aerender to render an AE comp. Use dryRun first to verify command.',
      inputSchema: z.object({
        projectPath: z.string(),
        compName: z.string(),
        outputPath: z.string(),
        aerenderBin: z.string().optional(),
        dryRun: z.boolean().default(true)
      })
    },
  • Configuration for aerenderBin read from environment variable AERENDER_BIN, used by the handler.
    aerenderBin: process.env.AERENDER_BIN ?? '',
  • The runCommand helper that spawns a child process and returns stdout/stderr/exit code, used to invoke the aerender binary.
    export function runCommand(command: string, args: string[], cwd?: string): Promise<{ code: number; stdout: string; stderr: string }> {
      return new Promise((resolve) => {
        const child = spawn(command, args, { cwd, shell: false });
        let stdout = '';
        let stderr = '';
        child.stdout.on('data', (d) => (stdout += d.toString()));
        child.stderr.on('data', (d) => (stderr += d.toString()));
        child.on('close', (code) => resolve({ code: code ?? -1, stdout, stderr }));
      });
    }
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only mentions dryRun and does not describe side effects (e.g., disk writes, external command execution), permission needs, or error behavior.

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?

The description is very concise, but it sacrifices necessary detail. The instruction about dryRun is front-loaded, but overall the brevity leads to under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 5 parameters, an external dependency, and no output schema, the description is grossly incomplete. It fails to cover prerequisites, return values, or potential errors.

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%, yet the description only addresses one parameter (dryRun) indirectly. projectPath, compName, outputPath, and aerenderBin are left unexplained.

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

Purpose5/5

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

The description clearly states 'Invoke aerender to render an AE comp', which gives a specific verb-resource-action combination. It distinguishes from sibling ae_generate_jsx (which generates scripts) by focusing on rendering.

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?

It provides the directive 'Use dryRun first to verify command,' which is a clear usage hint. However, it lacks comparison to sibling tools or guidance on when not to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Eliveral/codex-mcp-comfy-ae-video-factory-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server