MorphaReels

Move layer

move_layer

Destructive

Set a layer's static base transform. Writes x/y/w/h/rotation directly on image., video., and shapes.; for group. sets pivotX/pivotY (no width/height/rotation — use add_keyframe for group rotation). Also sets scale and opacity, which every layer kind carries. Note: when a layer has a keyframe track for a property, the track OVERRIDES the static value at every frame — use add_keyframe to animate, move_layer to set the un-animated default. A scale/opacity write over an existing track is REFUSED for that reason; pass clear_animation:true to replace the animation with the static value.

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": {
      "elementId": "<elementId>",
      "projectId": "<projectId>"
    },
    "name": "move_layer"
  }
}

Input Schema

Name	Required	Description
`x`	No	Centre x in the element's OWN frame. At root that is canvas coords (1080 wide); INSIDE A GROUP it is the group's space, so it is not where the layer sits on the canvas. inspect_layers reports both — write back the `x` it gave you, and read `canvas_x` for the on-canvas position.
`y`	No	Centre y in the element's OWN frame — canvas coords (1920 tall) at root, the group's space inside a group. See `x`.
`scale`	No	Uniform scale multiplier about the layer's pivot. 1 = natural size. Every layer kind carries it.
`width`	No	Width in px (must be > 0).
`height`	No	Height in px (must be > 0).
`opacity`	No	Layer opacity, 0..1 (values outside are allowed and clamp at paint time). Composes with any ancestor group's opacity.
`rotation`	No	Rotation in degrees, clockwise.
`elementId`	Yes	video.<id>, image.<id>, shapes.<id>, or group.<id>.
`projectId`	Yes	Opaque project id (a v4 UUID, from list_projects/create_project). Selects which existing project this call mutates.
`clear_animation`	No	true = each static value you pass REPLACES that property's keyframe track. For scale / opacity over a track, omitting it refuses the call rather than writing a value the animation would hide; for a leaf's x / y / width / height / rotation, omitting it writes the base under the track, where nothing paints it.

Output Schema

Name	Required	Description
`ok`	Yes	Whether the call succeeded.
`data`	No	The payload, shaped by the tool.
`note`	No	What to do next when not ready.
`error`	No	Why it failed.
`status`	No	For cache-backed readers: whether the answer was ready.
`editorUrl`	No	Opens this project in the editor.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedInput schema / properties / clear_animation / description

Previous value: -"Only meaningful when setting `scale` / `opacity` on a layer where that property is animated. true = the static value REPLACES the keyframe track. Omitted / false = the call is refused rather than writing a value the animation would hide."New value: +"true = each static value you pass REPLACES that property's keyframe track. For scale / opacity over a track, omitting it refuses the call rather than writing a value the animation would hide; for a leaf's x / y / width / height / rotation, omitting it writes the base under the track, where nothing paints it."

Changed2 schema fields changedSep 17, 2026

removedInput schema / properties / anonymousToken

Removed value: -{
-  "description": "The token create_anonymous_account returned. This connection has no Morpha key, so every call carries it.",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "elementId",
-  "projectId",
-  "anonymousToken"
-]New value: +[
+  "elementId",
+  "projectId"
+]

Changed1 schema field changedSep 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "The result envelope every Morpha tool returns.",
+  "properties": {
+    "data": {
+      "description": "The payload, shaped by the tool.",
+      "type": [
+        "object",
+        "array",
+        "string",
+        "number",
+        "boolean",
+        "null"
+      ]
+    },
+    "editorUrl": {
+      "description": "Opens this project in the editor.",
+      "type": "string"
+    },
+    "error": {
+      "description": "Why it failed.",
+      "type": "string"
+    },
+    "note": {
+      "description": "What to do next when not ready.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the call succeeded.",
+      "type": "boolean"
+    },
+    "status": {
+      "description": "For cache-backed readers: whether the answer was ready.",
+      "enum": [
+        "ready",
+        "not-ready"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedSep 11, 2026

addedInput schema / properties / anonymousToken

Added value: +{
+  "description": "The token create_anonymous_account returned. This connection has no Morpha key, so every call carries it.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "elementId",
-  "projectId"
-]New value: +[
+  "elementId",
+  "projectId",
+  "anonymousToken"
+]

First observedSep 7, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the destructiveHint=true annotation by naming exactly what is destroyed: static writes under a track 'where nothing paints it', and clear_animation:true replacing a keyframe track. It also discloses a refusal path ('A scale/opacity write over an existing track is REFUSED'), which is precisely the kind of behavior an agent cannot infer from annotations or schema.

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?

Front-loaded with the core operation, then per-kind scoping, then the override caveat — a sensible order. It is dense but every sentence carries information; the final sentence about clear_animation is slightly tangled and restates the refusal already implied earlier.

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

Completeness4/5

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

With an output schema present, return values need not be explained, and the mutation semantics, refusal path, and per-kind constraints are all covered. The gap is sibling disambiguation against move_layers and the unexplained pivot parameters, both of which an agent calling this correctly would want resolved.

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 baseline is 3, but the description adds genuine semantics: which properties apply per element kind (image/video/shapes get x/y/w/h/rotation; group gets pivot only) and that scale/opacity are universal. One flaw: it claims to set pivotX/pivotY for groups, yet no such properties exist in the input schema, which could mislead an agent about available parameters.

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?

States a specific verb and resource ('Set a layer's static base transform') and immediately scopes it by element kind, which lets an agent tell it apart from add_keyframe. However, it never distinguishes itself from the near-identically named sibling move_layers (batch move), leaving a real ambiguity for the most likely confusion.

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?

Explicitly routes the agent between this tool and add_keyframe: 'use add_keyframe to animate, move_layer to set the un-animated default', and explains when clear_animation is needed. Missing only the plural/batch alternative and any relationship to set_pivot, which the group note implies is a related decision point.

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

All MorphaReels tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?