Skip to main content
Glama
ConformLabs

surehand-mcp

Official
by ConformLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Batch edits

ae_batch
Destructive

Runs up to 200 After Effects tool steps in one call as one atomic undo and change report; repetitive or multi-part edits complete together, with rollback if a step fails.

Instructions

Run many steps in ONE call: each step is a tool with its arguments (any project/comp/layer/property/keyframe/effect/text/footage tool) or {tool: "ae_run_script", args: {code}}. All steps form a single undo step and return one change report. Atomic by default: if any step fails, everything is undone and you get the error of the failing step. Use it for repetitive or multi-part edits (e.g. style 30 layers, build a scene) to save round trips; for a single edit call the tool directly. Not usable as steps: tools that can't be part of an undo step (open/save project, undo/redo), renders and ae_checkpoint.

Input Schema

NameRequiredDescriptionDefault
nameNoUndo step name shown in After Effects (default "Surehand MCP Batch").
stepsYes1-200 steps run in order, each {tool, args} with the same args as calling that tool.
atomicNoUndo everything if a step fails (default true). false = keep successful steps and continue.
verboseNoReturn each step's full result (default: short summaries).
checkpointNoSave a project checkpoint before running (see ae_checkpoint).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.3
    • addedInput schema / properties / steps / description
      Added value: +"1-200 steps run in order, each {tool, args} with the same args as calling that tool."
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark this as destructive, non-read-only, non-idempotent, and open-world, and the description adds important batch semantics: all steps form one undo step, atomic rollback happens by default, and failures return the failing step's error. This adds meaningful behavioral context beyond the annotations without contradicting them.

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

Conciseness5/5

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

The description is front-loaded with the core batch behavior, then covers atomicity, usage guidance, and exclusions. It is dense but appropriately sized for a complex orchestration tool, with no wasted filler.

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

Completeness5/5

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

For a complex batch tool with no output schema, the description explains the return model as one change report, the atomic rollback behavior, and the failing-step error behavior. Combined with the fully described schema, it gives an agent enough context to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents the parameters. The description still adds useful meaning by explaining that each step is a tool plus arguments, that any project/comp/layer/property/keyframe/effect/text/footage tool is allowed, and that ae_run_script is a special step form.

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 states a specific verb and resource: running many tool steps in one batch call. It clearly distinguishes this from calling a single edit tool directly and explains the step structure, so an agent can identify the tool's role among siblings.

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

Usage Guidelines5/5

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

It explicitly says to use this for repetitive or multi-part edits, to call tools directly for a single edit, and names tool categories that cannot be used as steps. These are clear when-to-use, when-not-to-use, and alternative-selection instructions.

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

Deploy Server

Other Tools