MorphaReels

List projects

list_projects

Read-only

List projects as { id, name, editorUrl } entries. The id is what every other tool's projectId argument takes. name is the human-readable label shown in the editor's project picker ("Untitled" when no name has been set; ids are opaque and the editor never shows them). editorUrl is a link that opens that project in the editor. By default lists the user's OWN personal projects (those not in any workspace). Pass workspaceId (from list_workspaces) to instead list the projects that live in that workspace — including teammates' — each with the owner's ownerEmail. Call this when the user asks "what projects do I have?" or hasn't named a project but you need to operate on one.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`workspaceId`	No	Optional workspace id (from list_workspaces). When given, lists that workspace's projects instead of the caller's personal ones; requires membership. Omit for personal projects.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the call succeeded.
`data`	No	The caller's projects.
`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.

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

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 caller's projects.",
+      "properties": {
+        "claimUrl": {
+          "description": "Present only when the caller is an anonymous account: the link that hands its projects to a person.",
+          "type": "string"
+        },
+        "projects": {
+          "description": "One entry per project, newest first.",
+          "items": {
+            "description": "One project.",
+            "properties": {
+              "editorUrl": {
+                "description": "A link that opens this project in the editor.",
+                "type": "string"
+              },
+              "id": {
+                "description": "Opaque project id: what every other tool's `projectId` takes.",
+                "type": "string"
+              },
+              "name": {
+                "description": "The label a person sees (\"Untitled\" when unnamed). Refer to a project by this, never by its id.",
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "name",
+              "editorUrl"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "projects"
+      ],
+      "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"
+}

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

First observedSep 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds scoping behavior beyond that: personal projects are returned by default, workspaceId switches to workspace (including teammates') projects and adds ownerEmail, and name falls back to 'Untitled'. It stops short of describing pagination or volume limits.

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-loads what the tool returns before branching into the workspace case, and every sentence carries information. It is slightly dense with three field explanations plus two usage clauses, but nothing is wasted.

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, return structure needn't be re-described, and the description still supplies the field semantics, the default-vs-workspace behavior, and the triggering scenario. An agent has everything needed to call it 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 coverage is 100%, so the baseline is 3, and the description adds real meaning: the default (omit for personal projects), the membership requirement, that workspace results include teammates', and that each gains an ownerEmail. This exceeds what the single schema field states.

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 (list projects) and immediately clarifies the return shape and the meaning of each field (id maps to projectId, name is the editor label, editorUrl opens the project). It distinguishes the default personal-project listing from the workspace listing, so an agent can tell it apart from list_workspaces and the create/rename/delete_project siblings.

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 names the trigger ('what projects do I have?' or when no project is named but one must be operated on) and points to list_workspaces as the source of workspaceId. Both when-to-use and the alternative path are covered without inference.

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?