Skip to main content
Glama

MorphaReels

by ai.morphareels
OverviewDiscussionsAdmin

Render video

render_video
Destructive

Render the project to an MP4 on Morpha's servers, for an agent that has no browser to drive (a chat app, a Linux box). Returns { renderId, status: 'rendering', next } — call render_status with that renderId after about 30 seconds. It needs a subscription and draws on the account's render allowance, so a longer composition and a larger scale each use more of it. The editor renders the same MP4 with no allowance: every project result carries an editorUrl, and there the person can choose Share, then Download (Render MP4 on a phone), free and with no watermark. Renders at 2x the canvas by default, the same as the editor; pass scale: 1 for the canvas's own size, which is faster and uses less allowance. The allowance is checked before the render starts, so a render that would exceed it is refused up front rather than failing partway. Refused for a composition longer than 30 minutes, when the remaining allowance will not cover it, or while 3 renders are already running for this account. The finished file stays downloadable for 7 days, then it is deleted; the project stays and can be rendered again. The render downloads the project's fonts from their hosts, including a custom font's own URL (set_custom_font). Reference: https://morphareels.ai/docs/tools#rendervideopage-scale

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoOptional 0-based page index for a multi-page project. Omit for the project's active page; render one page per call.
scaleNoOptional output scale: 2 (the default) renders at twice the canvas, roughly 4K for a portrait project; 1 renders at the canvas's own size for a faster file that uses less allowance. Nothing else is accepted.
projectIdYesProject to render.

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. Changed1 schema field changed
    • changedInput schema / properties / scale / description
      Previous value: -"Optional output scale: 2 (the default) renders at twice the canvas, roughly 4K for a portrait project; 1 renders at the canvas's own size for a faster, cheaper file. Nothing else is accepted."New value: +"Optional output scale: 2 (the default) renders at twice the canvas, roughly 4K for a portrait project; 1 renders at the canvas's own size for a faster file that uses less allowance. Nothing else is accepted."
  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: -[
-  "projectId",
-  "anonymousToken"
-]New value: +[
+  "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. Changed1 schema field changed
    • addedInput schema / properties / scale
      Added value: +{
+  "description": "Optional output scale: 2 (the default) renders at twice the canvas, roughly 4K for a portrait project; 1 renders at the canvas's own size for a faster, cheaper file. Nothing else is accepted.",
+  "type": "number"
+}
  5. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only carry the generic write/open-world/destructive flags; the description goes well beyond them, disclosing subscription and allowance requirements, that longer compositions and larger scales cost more, upfront allowance checking, concurrency limits, 7-day file retention with the project surviving, and outbound font fetches. This is exactly the operational context annotations cannot express.

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?

Purpose and the follow-up call are front-loaded, and most sentences carry real operational payload. It is on the long side and the editor-alternative paragraph could be tighter, but there is little genuine 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 mutating, allowance-consuming, async render tool, the description covers prerequisites, async handoff, cost model, refusal conditions, and retention. With an output schema present it needn't explain the return payload, yet it still names the returned fields, so nothing an agent needs is missing.

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 page, scale, and projectId, including the scale=1 vs 2 tradeoff and 'nothing else is accepted'. The description reinforces scale's allowance implication but adds little semantic detail beyond what the schema states, 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 ('Render the project to an MP4 on Morpha's servers') and immediately scopes it to 'an agent that has no browser to drive'. It distinguishes itself from render_status (the follow-up) and from the editor's own export path, so an agent can route correctly without opening a schema.

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?

Explicit when-to-use ('an agent that has no browser to drive'), explicit alternative (the editor's Share/Download path, free and unwatermarked), explicit next step ('call render_status with that renderId after about 30 seconds'), and explicit refusal conditions (composition > 30 min, insufficient allowance, 3 renders already running). Nothing is left to inference.

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

All MorphaReels 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