MorphaReels

Upload audio

upload_audio

Destructive

Upload an audio track into a project from a public http(s) URL or a file attached in the chat, fetched server-side — the ONLY way to get an audio file's bytes into a project over MCP/HTTP (add_audio_overlay / update_audio_overlay only reference a file that is already uploaded). Pass url for a public http(s) link, or file for a file the person attached in the chat (a host that supports file inputs, such as ChatGPT, fills file with a temporary download link itself; do not ask the person for a URL to something they have attached). The target is the URL you pass and nothing else: Morpha's Worker fetches it with a plain HTTP GET, following redirects, and identifies itself as "Morpha/1.0 (+https://morphareels.ai; hello@morphareels.ai)". No third-party API is involved. The worker downloads the .mp3/.m4a/.wav/.ogg/.aac, stores it in the project's asset bucket under a new id, and returns { filename, name, sizeBytes, contentType }. Then pass the returned filename (the file's id, never shown to a person) to add_audio_overlay (add a second track) or update_audio_overlay { id, filename } (replace an existing track's file — find the id via describe_video's audio_overlays), with name as the track's name. A url must be a direct, publicly-fetchable http(s) link (not an auth-walled page). Buffered in Worker memory, so capped at 50 MB. A file on the person's own disk is uploaded in the editor. Reference: https://morphareels.ai/docs/tools#uploadaudiourl-file-name

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	Direct, publicly-fetchable http(s) URL of the audio file (.mp3/.m4a/.wav/.ogg/.aac). Pass either this or `file`.
`file`	No	A file the person attached in the chat (a host that supports file inputs, such as ChatGPT, fills this itself; do not type it). Pass either this or `url`.
`name`	No	Optional display name, what people see (e.g. Theme.mp3). Defaults to the attached file's name or the URL's file name. It never decides where the file is stored.
`projectId`	Yes	Project to add the audio to.

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.

Changed4 schema fields changedOct 11, 2026

addedInput schema / properties / file

Added value: +{
+  "description": "A file the person attached in the chat (a host that supports file inputs, such as ChatGPT, fills this itself; do not type it). Pass either this or `url`.",
+  "properties": {
+    "download_url": {
+      "description": "Temporary URL the host serves the file at.",
+      "type": "string"
+    },
+    "file_id": {
+      "description": "The host's id for the file.",
+      "type": "string"
+    },
+    "file_name": {
+      "description": "The file's own name, when the host knows it.",
+      "type": "string"
+    },
+    "mime_type": {
+      "description": "The file's media type, when the host knows it.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "download_url",
+    "file_id"
+  ],
+  "type": "object"
+}

changedInput schema / properties / name / description

Previous value: -"Optional display name, what people see (e.g. Theme.mp3). Defaults to the URL's file name. It never decides where the file is stored."New value: +"Optional display name, what people see (e.g. Theme.mp3). Defaults to the attached file's name or the URL's file name. It never decides where the file is stored."

changedInput schema / properties / url / description

Previous value: -"Direct, publicly-fetchable http(s) URL of the audio file (.mp3/.m4a/.wav/.ogg/.aac)."New value: +"Direct, publicly-fetchable http(s) URL of the audio file (.mp3/.m4a/.wav/.ogg/.aac). Pass either this or `file`."

changedInput schema / required

Previous value: -[
-  "projectId",
-  "url"
-]New value: +[
+  "projectId"
+]

Changed2 schema fields changedSep 17, 2026

removedInput schema / properties / filename

Removed value: -{
-  "description": "Optional stored filename (.mp3/.m4a/.wav/.ogg/.aac). Defaults to the basename of the URL path; sanitised to lowercase a-z0-9._-.",
-  "type": "string"
-}

addedInput schema / properties / name

Added value: +{
+  "description": "Optional display name, what people see (e.g. Theme.mp3). Defaults to the URL's file name. It never decides where the file is stored.",
+  "type": "string"
+}

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

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

First observedSep 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations cover the safety profile (readOnly=false, openWorld=true, destructive=true), yet the description adds substantial behavioral detail beyond them: server-side plain HTTP GET with redirects, a named user-agent, no third-party API, buffered in Worker memory with a 50 MB cap, and storage in the project's asset bucket under a new id. This is exactly the extra context annotations cannot carry.

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?

Front-loaded with purpose, then usage, then the fetch mechanism, then the downstream handoff, so the structure is sound. It is dense and runs long, with some mechanism detail (user-agent string, reference URL) that borders on surplus, keeping it out of the top score.

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 tool with nested objects, four parameters, and an output schema, the description supplies everything needed: accepted formats, source options, size cap, storage behavior, and the exact next step. Return-value details are even redundantly restated despite the output schema, so nothing is missing.

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, but the description adds real semantics: `url` must be a direct, publicly-fetchable link (not an auth-walled page), `file` is host-populated rather than typed, and `name` never decides storage location. These caveats are not fully captured by the schema text alone.

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+resource ('Upload an audio track into a project') and immediately distinguishes itself from siblings: it is 'the ONLY way to get an audio file's bytes into a project over MCP/HTTP,' while add_audio_overlay/update_audio_overlay only reference an already-uploaded file. An agent can route correctly without opening any 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?

Explicitly specifies the two mutually exclusive paths (`url` for a public http(s) link, `file` for a chat-attached file) and warns not to ask the person for a URL to something they attached. It also states the downstream handoff (pass returned `filename` to add_audio_overlay or update_audio_overlay), so both when-to-use and what-comes-next are covered.

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

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