Skip to main content
Glama
AE Motion MCP
by dha-aa

Set Comp

set_comp
DestructiveIdempotent

Adjust After Effects composition settings by passing only the fields to change, including size, frame rate, duration, background, renderer, work area, motion blur, and frame blending.

Instructions

Change comp settings; only the fields you pass change. work_area must fit inside the comp. motion_blur and frame_blending are the comp switches the layer switches need to render; shutter_angle default 180.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "comp_id": "<comp_id>"
    },
    "name": "set_comp"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNo
nameNo
widthNo
heightNo
comp_idYes
bg_colorNo
durationNo
rendererNo3D renderer name; an unknown one lists those installed
work_areaNo
motion_blurNo
pixel_aspectNo
shutter_angleNo
shutter_phaseNo
frame_blendingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.26.0
    • addedInput schema / properties / renderer / description
      Added value: +"3D renderer name; an unknown one lists those installed"
  2. Changed1 schema field changedv2.25.0
    • addedInput schema / properties / renderer
      Added value: +{
      +  "type": "string"
      +}
  3. First observedv2.22.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds genuinely useful behavior not in the schema, namely merge-not-replace semantics, the work_area containment constraint, and the relationship between comp-level motion_blur/frame_blending and layer switches. It never explains what the destructive hint actually means here (e.g. whether shrinking width/height displaces or clips layers), which is the biggest behavioral gap for a flagged-destructive mutation.

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?

Three compact, front-loaded sentences with no filler; the mutation semantics lead and the constraints follow. The phrasing is terse to the point of being telegraphic ("the comp switches the layer switches need to render"), which costs a little readability but wastes no words.

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

Completeness3/5

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

For a 14-parameter destructive mutation with no output schema and near-zero schema descriptions, the definition should cover more: units for duration/fps, accepted formats for bg_color, and what a successful call returns or how the comp ends up. The partial-update rule and one containment constraint are a solid core, but the definition stops short of complete.

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

Parameters3/5

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

Schema coverage is only 7%, so the description carries most of the burden; it partially delivers by clarifying work_area's nesting constraint, the shutter_angle default of 180, and the render-side meaning of motion_blur/frame_blending. Nine-plus parameters (fps, width, height, bg_color, duration, pixel_aspect, shutter_phase, name, comp_id) get no meaning, units, or format guidance, leaving a substantial compensation gap.

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?

"Change comp settings" names a specific verb and resource, and "only the fields you pass change" pins down the partial-update semantics that separate it from create_comp in spirit. It never names a sibling outright, so the agent has to infer the create/read/write split, but the purpose itself 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?

The partial-update rule plus "work_area must fit inside the comp" tells the agent how to call it safely, which is a form of usage guidance. There is no explicit when-to-use or when-not-to-use statement and no routing to get_comp for inspection or create_comp for new comps, so the guidance remains implied.

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