Skip to main content
Glama

Morpha

by ai.morphareels
OverviewDiscussionsAdmin

Add video layer

add_video_layer

Add a video layer. The clip must already be uploaded (the morphareels-sdk's client.addVideo, or the 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
NameRequiredDescriptionDefault
xYesCentre x in 1080-wide base coords.
yYesCentre y in 1920-tall base coords.
clipYesThe stored clip filename an upload returned (an id such as 3f2a9c1e-….mp4, or an older project's own name).
nameNoOptional label people see in the Inspector and Timeline: pass the upload's returned `name`.
widthYesWidth in px (must be > 0).
heightYesHeight in px (must be > 0).
projectIdYesOpaque project id (a v4 UUID, from list_projects/create_project). Selects which existing project this call mutates.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the call succeeded.
dataNoThe payload, shaped by the tool.
noteNoWhat to do next when not ready.
errorNoWhy it failed.
statusNoFor cache-backed readers: whether the answer was ready.
editorUrlNoOpens this project in the editor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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`."
  2. Changed2 schema fields changed
    • 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"
+]
  3. Changed1 schema field changed
    • 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"
+}
  4. Changed2 schema fields changed
    • 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"
+]
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint=false (mutating) and destructiveHint=false. The description adds meaningful context beyond this: the upload prerequisite, the filename/name mapping, and that duplication auto-assigns a fresh id. This extra detail about side effects (fresh id) is valuable, so a 4 is appropriate.

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 sentences, front-loaded with the core purpose, followed by prerequisite, parameter mapping, and a special case. No redundancy or wasted words – every sentence contributes.

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?

The description covers the only non-obvious aspects (upload mapping, duplication) while the schema handles x/y/width/height/projectId. An output schema exists, so return format needs no explanation. Nothing missing for correct invocation.

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. The description adds extra meaning by linking clip to the upload's filename and name to the upload's label, and explains the duplication reuse case. This goes beyond the schema descriptions, earning a 4.

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 opens with 'Add a video layer' – a specific verb and resource that clearly distinguishes it from sibling add_* tools (add_image_layer, add_text_layer, etc.). It further clarifies scope by explaining the upload prerequisite and how to map upload results to parameters.

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?

Provides clear usage context: the clip must be uploaded first, and it explains the duplication workflow (reuse clip filename). It does not explicitly contrast with alternative add_* tools, but the purpose is unambiguous enough that an agent can infer when to use it. Lacks explicit 'when not to use' guidance, so a 4 rather than 5.

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

All Morpha toolsInspect
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