Morpha

Render status

render_status

Read-only

Check a server render started by render_video, and get its download link. Returns { ok: true, status: 'not-ready' } while it is still rendering (wait and call again), or { ok: true, status: 'ready', data: { downloadUrl, editorUrl, expiresAt, videoSeconds, scale, chargedCents } } once the MP4 is ready. downloadUrl is a plain https link needing no Morpha account — give it to the person; it stops working when the render is deleted at expiresAt (7 days). chargedCents is what the render cost the subscription. A render that failed answers ok:false with a plain reason and is never charged. Only the account that started a render can read it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`renderId`	Yes	The renderId render_video returned.

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: -[
-  "renderId",
-  "anonymousToken"
-]New value: +[
+  "renderId"
+]

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"
+}

AddedSep 12, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already mark this read-only and non-destructive, and the description adds substantial behavioral context beyond them: the polling contract ('not-ready' vs 'ready'), the 7-day expiry and deletion behavior of downloadUrl, the billing semantics of chargedCents, the never-charged failure path, and the ownership restriction. This is exactly the kind of runtime behavior an agent needs to use the tool correctly.

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 dense (roughly 100 words) but every sentence carries information: purpose, polling behavior, both response shapes, downloadUrl semantics with recipient and expiry, cost disclosure, failure behavior, and access control. It front-loads the purpose and is ordered logically from call to final state. A couple of sentences are run-on but no filler exists.

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 single-parameter polling tool, the description covers everything an agent needs: what triggers a call, what to do on pending, what ready and failed responses look like, how to handle the download link, expiry timing, billing, and access control. The output schema also exists and the description already mirrors its key structure, so no return-value documentation gap remains.

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% with renderId documented as 'The renderId render_video returned.' The description reinforces that the value must come from render_video and adds the ownership constraint ('Only the account that started a render can read it'), which clarifies which renderId values are valid. This slightly exceeds the baseline for fully-covered schemas.

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: 'Check a server render started by render_video, and get its download link.' It names the originating sibling tool, which immediately distinguishes it from the other status-style sibling (clip_processing_status) since this one is tied specifically to render_video's output.

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 clear usage context: it is for renders started by render_video, should be polled ('wait and call again' while not-ready), and is restricted to the account that started the render. It does not explicitly name alternatives or exclusions (e.g., clip_processing_status), but the render_video reference makes the intended use unambiguous.

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?