Morpha

Freeze frame

freeze_frame

Destructive

Freeze the picture at a frame: the clip is CUT there and a still of that frame is inserted between the halves, pushing everything after it later (the NLE 'frame hold'). This is how you hold a moment — play, freeze, continue. The still is an ordinary IMAGE layer showing that frame for holdFrames (default 150 = 5s at 30fps), so you resize, split, move or delete it like any other layer. image is the filename of a PNG of that frame, already uploaded to the project's assets — rendering one needs a browser, so capture and upload it first. The reply's frozenSourceFrame is the SOURCE frame that was frozen, which differs from frame on a retimed clip. frame must be strictly inside the clip.

Input Schema

TableJSON Schema

Name	Required	Description
`frame`	Yes	Project-timeline frame to freeze at — must be strictly inside the clip.
`image`	Yes	Filename of an already-uploaded PNG of the frozen frame, in the project's assets.
`elementId`	Yes	video.<id> to freeze.
`projectId`	Yes	Opaque project id (a v4 UUID, from list_projects/create_project). Selects which existing project this call mutates.
`holdFrames`	No	How long the still holds, in frames. Defaults to 150 (5s at 30fps), the same default every added clip gets.

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

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",
-  "frame",
-  "image",
-  "projectId",
-  "anonymousToken"
-]New value: +[
+  "elementId",
+  "frame",
+  "image",
+  "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",
-  "frame",
-  "image",
-  "projectId"
-]New value: +[
+  "elementId",
+  "frame",
+  "image",
+  "projectId",
+  "anonymousToken"
+]

First observedSep 7, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description discloses the destructive behavior (clip is cut), matches the destructiveHint annotation, and explains the resulting image layer is editable ('resize, split, move or delete it like any other layer'). It also clarifies the output field 'frozenSourceFrame' differs from 'frame' on retimed clips, adding value beyond annotations. No contradictions with the annotations.

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?

The description is thorough but not bloated. It front-loads the core action, then explains the mechanism, the layer nature, the prerequisite, the output field, and the constraint. Each sentence adds value, though it's slightly longer than minimal. It earns a 4 for being appropriately detailed without waste.

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?

For a destructive tool with 5 parameters and an output schema, the description covers all critical aspects: the timeline effect, the layer editability, the image upload prerequisite, the default holdFrames, the output semantics, and the frame constraint. Nothing essential is missing for correct invocation.

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 describes each parameter's meaning (frame, image, elementId, projectId, holdFrames). The description adds context (e.g., the still is an image layer, holdFrames default matches), but these are largely restatements. It doesn't add significant new semantics beyond the schema, so baseline 3 is appropriate.

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 action: 'Freeze the picture at a frame: the clip is CUT there and a still of that frame is inserted between the halves.' It specifies the resource (clip) and the effect (frame hold), and distinguishes it from other layer operations by describing the unique NLE behavior. No sibling tool does this, so it's 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?

The description explains when to use it ('This is how you hold a moment — play, freeze, continue') and provides a clear prerequisite: the PNG must be uploaded first ('rendering one needs a browser, so capture and upload it first'). It doesn't mention alternatives, but there is no obvious competing tool in the sibling list, so this is sufficient.

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

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