Skip to main content
Glama

Morpha

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 — you never choose or name it; refer to the project by its 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.

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.4/5.0
Behavior4/5

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

The annotations only indicate that the tool is not read-only, not open-world, and not destructive, which is minimal. The description goes beyond this by detailing the cloning behavior (copies JSON, assets, clips), workspace inheritance and fallback rules, failure conditions (view-only source), and the lack of auto-refresh in the editor. This is substantial behavioral context beyond the annotations, though it does not specify error codes or side effects on the source project (which is non-destructive).

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 detailed but remains focused and front-loaded: it leads with the core purpose and returns value, then explains cloning and workspace placement. It is longer than a typical definition due to necessary complexity, but every sentence serves a purpose (e.g., the warning about view-only source). Minor redundancy exists with the schema descriptions but is acceptable for the added decisional guidance.

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?

Given the tool's complexity—three parameters with conditional behavior, workspace inheritance, failure modes, and editor refresh behavior—the description covers all necessary decision points. The output schema exists, so the return value is structurally documented. The description is complete enough for an agent to invoke the tool correctly across all scenarios (blank, clone, workspace assignment, personal copy).

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 description coverage is 100%, so the schema already documents all three parameters. The description adds nuance by clarifying the interaction between workspaceId and fromProjectId, and the fallback behavior, which is valuable. However, since the schema already provides detailed descriptions for each parameter, the added semantic value is incremental, justifying a baseline of 3.

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 states a specific action ('create a new project'), identifies the resource, and explains that it returns a server-minted UUID. It clearly differentiates between creating a blank project and cloning, and names the sibling tool duplicate_project to disambiguate. This is explicit and distinguishes it from other project-related tools like duplicate_project and open_project.

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 explicitly instructs when to pass fromProjectId (to clone) versus omitting it (blank project), how to use workspaceId to control placement, and warns that cloning a source in a view-only workspace will fail unless workspaceId:null is passed. It contrasts with duplicate_project and provides clear decision logic, leaving no ambiguity for the agent.

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