MorphaReels

Add video layer

add_video_layer

Add a video layer. The clip must already be uploaded; clips are uploaded in the MorphaReels editor. An upload returns { filename, name }: pass filename (the stored clip's id) as clip, and name as the layer's label. To duplicate an existing layer, reuse its clip filename — the editor auto-assigns a fresh id.

Input Schema

TableJSON Schema

Name	Required	Description
`x`	Yes	Centre x in 1080-wide base coords.
`y`	Yes	Centre y in 1920-tall base coords.
`clip`	Yes	The stored clip filename an upload returned (an id such as 3f2a9c1e-….mp4, or an older project's own name).
`name`	No	Optional label people see in the Inspector and Timeline: pass the upload's returned `name`.
`width`	Yes	Width in px (must be > 0).
`height`	Yes	Height in px (must be > 0).
`projectId`	Yes	Opaque project id (a v4 UUID, from list_projects/create_project). Selects which existing project this call mutates.

Output Schema

TableJSON 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.

Changed2 schema fields changedSep 17, 2026

changedInput schema / properties / clip / description

Previous value: -"Clip filename in the project's clips bucket, e.g. demo.mp4."New value: +"The stored clip filename an upload returned (an id such as 3f2a9c1e-….mp4, or an older project's own name)."

changedInput schema / properties / name / description

Previous value: -"Optional friendly label shown in the Inspector + Timeline."New value: +"Optional label people see in the Inspector and Timeline: pass the upload's returned `name`."

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: -[
-  "clip",
-  "x",
-  "y",
-  "width",
-  "height",
-  "projectId",
-  "anonymousToken"
-]New value: +[
+  "clip",
+  "x",
+  "y",
+  "width",
+  "height",
+  "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: -[
-  "clip",
-  "x",
-  "y",
-  "width",
-  "height",
-  "projectId"
-]New value: +[
+  "clip",
+  "x",
+  "y",
+  "width",
+  "height",
+  "projectId",
+  "anonymousToken"
+]

First observedSep 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds real context beyond that: the upload prerequisite, the shape of the upload return ({ filename, name }), and that the editor auto-assigns a fresh id on duplication. It does not describe failure modes (e.g. what happens with an invalid clip), keeping it from a 5.

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-loads the action, then prerequisite, then the parameter mapping, then the duplication shortcut. Each sentence earns its place, though the clip/name mapping is somewhat dense relative to what the schema already conveys.

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 prerequisite plus id semantics are covered. The main remaining gap is the absence of any failure/validation behavior, which is minor for this create operation.

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 100% and the schema already documents each parameter, including that `clip` is a stored filename and `name` is the label. The description's mapping of the upload's { filename, name } onto `clip`/`name` largely restates that, so the baseline 3 applies.

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 and resource ('Add a video layer') that is immediately distinguishable from the sibling add_image_layer, add_text_layer, and add_audio_overlay. The scope 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 Guidelines4/5

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

Gives a clear prerequisite ('The clip must already be uploaded; clips are uploaded in the MorphaReels editor') and a specific alternative path ('To duplicate an existing layer, reuse its clip filename'). It does not explicitly name sibling tools or state when-not to use this tool, but the context is strong.

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?