Skip to main content
Glama

Morpha

by ai.morphareels
OverviewDiscussionsAdmin

Create upload link

create_upload_link
Destructive

Put a file from the caller's own disk into a project: an image (.png/.jpg/.jpeg/.gif/.webp/.svg), an audio track (.mp3/.m4a/.wav/.ogg/.aac) or a font (.woff2/.woff/.ttf/.otf). Returns { uploadUrl, filename, name, command, expiresAt, maxBytes }. Run command from a shell (a curl line that PUTs the file's raw bytes to uploadUrl), then pass the returned filename (the file's id, never shown to a person) to add_image_layer, add_audio_overlay or set_custom_font. The link takes one file, stored under the id it was minted with, for 15 minutes; a second upload in that window replaces the first. The upload is checked as an editor drag-drop is: size cap (16 MB for an image or font, 50 MB for audio), SVG safety, storage quota. A client with no shell passes a public URL to upload_image or upload_audio instead. A video clip is not taken here, because its preview proxy is built on the caller's machine: use the morphareels-sdk's client.addVideo. Reference: https://morphareels.ai/docs/tools#createuploadlinkname

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe file's own name or path on disk, with its extension (e.g. hero.jpg). `command` uploads that path, people see its last segment, and the file is stored under a new id.
projectIdYesProject the file goes into.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the call succeeded.
dataNoA link that takes one file from the caller's disk, and the command that sends it.
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. Changed7 schema fields changed
    • removedInput schema / properties / filename
      Removed value: -{
-  "description": "The file's own name with its extension (e.g. hero.jpg). Stored lowercased with unsafe characters replaced; the result's `filename` is the stored name.",
-  "type": "string"
-}
    • addedInput schema / properties / name
      Added value: +{
+  "description": "The file's own name or path on disk, with its extension (e.g. hero.jpg). `command` uploads that path, people see its last segment, and the file is stored under a new id.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "projectId",
-  "filename"
-]New value: +[
+  "projectId",
+  "name"
+]
    • changedOutput schema / properties / data / properties / filename / description
      Previous value: -"The stored name: what add_image_layer, add_audio_overlay and set_custom_font take."New value: +"The file's id: what add_image_layer, add_audio_overlay and set_custom_font take. Never shown to a person."
    • addedOutput schema / properties / data / properties / name
      Added value: +{
+  "description": "The file's display name, what people see: the last segment of the name you passed.",
+  "type": "string"
+}
    • removedOutput schema / properties / data / properties / renamedFrom
      Removed value: -{
-  "description": "Present when sanitising changed the name you passed: what you passed.",
-  "type": "string"
-}
    • changedOutput schema / properties / data / required
      Previous value: -[
-  "uploadUrl",
-  "filename",
-  "contentType",
-  "maxBytes",
-  "expiresAt",
-  "command"
-]New value: +[
+  "uploadUrl",
+  "filename",
+  "name",
+  "contentType",
+  "maxBytes",
+  "expiresAt",
+  "command"
+]
  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",
-  "filename",
-  "anonymousToken"
-]New value: +[
+  "projectId",
+  "filename"
+]
  3. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond annotations (destructiveHint=true), the description reveals concrete behavioral details: the link expires after 15 minutes, a second upload replaces the first, and uploads are subject to size caps, SVG safety checks, and storage quota. This is exactly the kind of behavioral context annotations alone cannot provide.

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 dense but every sentence contributes: accepted types, return fields, usage workflow, replacement/expiry behavior, validation constraints, alternatives, and a documentation link. It is front-loaded with the core purpose and wastes no words.

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?

With an output schema present for return values, the description only needs to explain behavior not already structured. It covers the upload flow, time-to-live, overwrite semantics, size limits, and alternative tools, leaving no critical gap for an agent to call the tool 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 description coverage is 100%, so the baseline is 3. The description adds meaning by explaining that 'name' is the on-disk path used by the returned command, that only its last segment is shown to people, and that the file is stored under a fresh id. This goes beyond the schema's description, though projectId gets no extra clarification.

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 opens with a specific verb and resource: 'Put a file from the caller's own disk into a project' and enumerates accepted file types. It also distinguishes itself from near siblings by explicitly routing shell-less clients to upload_image/upload_audio and video clips to client.addVideo.

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?

The description gives explicit when-to-use and when-not-to-use guidance: clients without a shell should use upload_image/upload_audio instead, and video clips must go through morphareels-sdk's client.addVideo. It also explains the full workflow: run the returned command, then pass the filename to add_image_layer, add_audio_overlay, or set_custom_font.

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