Skip to main content
Glama

Morpha

by ai.morphareels
OverviewDiscussionsAdmin

Set video clip

set_video_clip
Destructive

Repoint an existing video layer at a different uploaded clip — keeps the layer's id, position, size, animations, styles, and trim window; only the source mp4 changes. The clip must already be uploaded (the editor's Add video, or the morphareels-sdk's client.addVideo); pass the filename the upload returned, and its name as the label. Use this to swap a video layer's source WITHOUT losing its keyframes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clipYesThe uploaded clip's id: the `filename` its upload returned.
nameNoOptional label people see for the layer: pass the upload's returned `name`. Omit to keep the current label; null or an empty string clears it.
elementIdYesVideo layer id, video.<id>.
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. mickey-tiktok.mp4."New value: +"The uploaded clip's id: the `filename` its upload returned."
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Optional label people see for the layer: pass the upload's returned `name`. Omit to keep the current label; null or an empty string clears it.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  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: -[
-  "elementId",
-  "clip",
-  "projectId",
-  "anonymousToken"
-]New value: +[
+  "elementId",
+  "clip",
+  "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: -[
-  "elementId",
-  "clip",
-  "projectId"
-]New value: +[
+  "elementId",
+  "clip",
+  "projectId",
+  "anonymousToken"
+]
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

The annotations already mark destructiveHint=true, and the description adds valuable context by specifying exactly what changes ('only the source mp4 changes') and what is preserved (id, position, size, animations, styles, trim window). It also notes the clip must be uploaded, implying a failure condition. However, it does not mention potential error outcomes or permission requirements, which would have strengthened transparency further.

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?

The description is three sentences, with the main purpose and scoping constraint front-loaded. It efficiently conveys the action, the preservation guarantee, the prerequisite, and the key parameter guidance. Every sentence adds essential information without redundancy.

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?

For a mutation tool with 4 parameters and an output schema, the description covers the core behavior, the precondition, and the parameter semantics. It does not explicitly mention error handling or side effects beyond the layer change, but the output schema likely covers return values. Given the complexity, this is sufficiently complete for an agent to invoke correctly.

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 all parameters are described in the schema. The description adds meaning by explaining that 'clip' is the upload's filename and 'name' is the label (optional, can be null/empty to clear). It also clarifies that elementId is the video layer id (video.<id>). This context helps the agent understand the provenance and format of the parameters beyond the schema's bare descriptions.

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 clearly states the verb 'repoint' with the specific resource 'existing video layer' and the target 'different uploaded clip'. It distinguishes from siblings by emphasizing it keeps the layer's id, position, size, animations, styles, and trim window while only changing the source mp4. This differentiates it from add_video_layer, set_video_layer_trim, and similar tools.

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

Usage Guidelines5/5

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

It explicitly states the use case: 'Use this to swap a video layer's source WITHOUT losing its keyframes.' It also provides prerequisites (the clip must already be uploaded) and references how to obtain the required parameters (via upload's filename and name). This gives clear guidance on when to invoke this tool and what conditions must be met.

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