Skip to main content
Glama

MorphaReels

by ai.morphareels
OverviewDiscussionsAdmin

Create project

create_project

Create a new project and return its server-minted id. The id is an opaque v4 UUID assigned automatically, not chosen by the caller; people see the project's name. By default this mints a fresh BLANK project (empty canvas, no layers) — creation is independent from cloning. Pass fromProjectId ONLY when you want to clone: the new project then copies that project's JSON, uploaded assets, and uploaded clips, and — like duplicate_project — FOLLOWS THE SOURCE'S workspace by default (cloning a team project stays in that team; a blank project is personal). Pass workspaceId (from list_workspaces) to place it in a specific workspace instead — requires an edit-capable role there — or null to force it into the caller's personal space. If the clone source lives in a workspace you can only view, the call FAILS rather than silently making a personal copy — pass workspaceId:null for a personal copy. The user's editor session won't auto-refresh — they'll need to reload to see the new project in the picker. Options or versions of one video (styles to pick from, hooks, languages) are pages of ONE project (add_page, duplicate_index), not new projects: the chat preview turns pages, and separate projects cannot be flicked between.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoRecommended human-readable label, shown verbatim in the editor's project picker (the only user-facing handle for the project). Omit and the picker falls back to the opaque id.
workspaceIdNoWhere to place the project. Omit to FOLLOW THE SOURCE (a clone inherits its source's workspace; a blank project is personal). A workspace id (from list_workspaces) places it there — requires an edit-capable role. null forces the caller's personal space.
fromProjectIdNoOptional id of an existing project to CLONE (copies its JSON + uploaded assets + clips). Omit to create a fresh blank project.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the call succeeded.
dataNoThe project that was created, blank or cloned.
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. 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"
-}
    • removedInput schema / required
      Removed value: -[
-  "anonymousToken"
-]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "The result envelope every Morpha tool returns.",
+  "properties": {
+    "data": {
+      "description": "The project that was created, blank or cloned.",
+      "properties": {
+        "assetsCopied": {
+          "description": "How many assets the clone copied.",
+          "type": "number"
+        },
+        "claimUrl": {
+          "description": "Present only when the caller is an anonymous account: the link that hands its projects to a person.",
+          "type": "string"
+        },
+        "clipsCopied": {
+          "description": "How many source clips the clone copied.",
+          "type": "number"
+        },
+        "editorUrl": {
+          "description": "A link that opens this project in the editor.",
+          "type": "string"
+        },
+        "fromProjectId": {
+          "description": "The project it was cloned from, or null for a blank one.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "projectId": {
+          "description": "The new project's opaque id.",
+          "type": "string"
+        },
+        "workspaceId": {
+          "description": "The workspace it landed in, or null for Personal.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "projectId",
+        "editorUrl"
+      ],
+      "type": "object"
+    },
+    "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"
+}
  3. Changed2 schema fields changed
    • 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"
+}
    • addedInput schema / required
      Added value: +[
+  "anonymousToken"
+]
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare it is not read-only and not destructive; the description adds substantial context beyond that – what gets copied on clone (JSON, assets, clips), workspace inheritance, the edit-role requirement, the hard failure for view-only sources, and the editor not auto-refreshing. That is exactly the kind of behavioral detail an agent cannot infer from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and return value, but the single block mixes creation, cloning, workspace rules, and page-vs-project guidance; it is dense and could be broken into clearer sentences. Every sentence is relevant, but the structure is harder to scan than ideal.

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 mutation tool with an output schema and rich sibling set, the description covers default behavior, override paths, failure modes, and disambiguation from related tools. Nothing an agent needs in order to call it correctly appears to be 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; the description nevertheless adds meaning – that name is user-facing, that fromProjectId triggers cloning with specific copy semantics, and the three-way behavior of workspaceId (omit=follow source, id=place, null=personal). It does not add syntax beyond the schema but reinforces the operational consequences of each parameter.

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 ('Create a new project') and immediately clarifies the returned id is server-minted and opaque. It explicitly contrasts with sibling duplicate_project and with add_page/duplicate_index, so an agent can tell this apart from cloning or page-level operations.

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?

Gives explicit when/when-not conditions: blank project by default, pass fromProjectId ONLY to clone, pass workspaceId or null to control placement, and use add_page/duplicate_index for versions of one video. It names the alternatives (duplicate_project, add_page, duplicate_index) and the failure mode when cloning a view-only workspace project.

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