Skip to main content
Glama
dha-aa

AE Motion MCP

by dha-aa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Set Property

set_property
DestructiveIdempotent

Set a static value, or a value at time (creates/updates a keyframe). Animated properties need time. Use set_text for text. layer_ids sets the same property on many layers in one call (all checked first).

Instructions

Set a static value, or a value at time (creates/updates a keyframe). Animated properties need time. Use set_text for text. layer_ids sets the same property on many layers in one call (all checked first).

Input Schema

NameRequiredDescriptionDefault
pathYes
timeNo
valueYesnumber, boolean, number array, or for path properties a shape spec as add_mask's shape
layer_idNo
layer_idsNoSame comp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.23.0
    • changedInput schema / properties / value / anyOf
      Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "items": {
-      "type": "number"
-    },
-    "type": "array"
-  },
-  {
-    "additionalProperties": {},
-    "type": "object"
-  }
-]New value: +[
+  {
+    "type": [
+      "number",
+      "string",
+      "boolean",
+      "object"
+    ]
+  },
+  {
+    "items": {
+      "type": "number"
+    },
+    "type": "array"
+  }
+]
  2. First observedv2.22.0

TDQS

A4.3/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: it discloses that supplying `time` creates or updates a keyframe, and that layer_ids applies the same property to many layers with all targets checked first (pre-validation before mutation). It does not warn that an existing keyframe/static value is overwritten, which matters given destructiveHint=true.

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?

Three short sentences, front-loaded with the core behavior, then the time dependency, then the sibling pointer and the batch caveat. No filler.

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 destructive, idempotent mutation with no output schema and 40% schema coverage, the description covers keyframe and batch semantics but leaves the `path` addressing format, overwrite/destructive consequences, and failure behavior underspecified.

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 only 40%, but the description compensates for the most misleading params: `time` is defined as the keyframe time and required for animated properties, and `layer_ids` is defined as same-comp multi-layer targeting with upfront validation. `path` format and `layer_id` vs `layer_ids` precedence remain 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?

States a specific verb (Set) and resource (a property value, static or keyframed) and explicitly distinguishes itself from set_text and from keyframe-only siblings. An agent can tell it apart from set_keyframes/edit_keyframes without opening a schema, since 'creates/updates a keyframe' is called out as a mode of this tool rather than a separate one.

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

Usage Guidelines4/5

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

Gives a concrete rule ('Animated properties need `time`') and routes text work to set_text. However it does not say when to prefer set_keyframes/batch/animate over repeated calls with layer_ids, nor what to do when a property is animated but no time is supplied.

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