Morpha

List versions

list_versions

Read-only

List every saved version of a project, newest-first. Returns summaries (id, name, timestamp, source, kind, version_number, cp) — not the inner project JSON. kind is "bookmark" (deliberate save, gets a v label, partner-pinnable in the embed) or "auto" (editor auto-snapshot every ~10 mutations, restore-only). version_number is bookmark-only and stable for the lifetime of that version — deletes leave gaps, numbers never re-shuffle. cp names which pages the version changed (comma-joined 8-char page-id prefixes; "*" = page order only; absent = unknown, treat as all pages). Use the returned id (or v<version_number> shorthand) with restore_version / rename_version / delete_version.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`projectId`	Yes	Project whose versions to list.

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.

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

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

First observedSep 7, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Although annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, the description goes far beyond by detailing the semantics of the returned fields: 'kind' differentiates bookmarks (deliberate saves, partner-pinnable) from auto-snapshots (restore-only), 'version_number' stability rules (deletes leave gaps, numbers never re-shuffle), and 'cp' meaning (page changes, special values like '*' and absence). It also discloses that the tool returns summaries, not the inner project JSON. This is rich behavioral context that helps the agent interpret results correctly.

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 front-loaded with the core function ('List every saved version of a project, newest-first') and then systematically explains each relevant field. Every sentence provides necessary context (kind distinctions, version_number stability, cp semantics, and downstream usage). The length is justified by the complexity of the output fields; it is not verbose or redundant.

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 that an output schema exists (as indicated by 'Has output schema: true'), the description does not need to detail the return structure. It covers all essential operational aspects: what is returned, field semantics, ordering, and how to use the output with related tools. Combined with the annotations, there is nothing an agent needs to call this tool correctly that is missing.

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?

The schema already provides 100% coverage for projectId ('Project whose versions to list.'), so the description does not need to add parameter details. The description does not explicitly restate the parameter, but the baseline for fully covered parameters is 3, and no additional semantic value is required or added.

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 ('List every saved version of a project'), the resource ('saved versions of a project'), and the ordering ('newest-first'). It clearly distinguishes itself from sibling tools like save_version, restore_version, rename_version, and delete_version by focusing on the read-only listing nature and explicitly noting it returns summaries, not the inner project JSON.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage context by explaining the returned fields (kind, version_number, cp) and explicitly directs the user to use the returned id with restore_version, rename_version, or delete_version. It does not explicitly state when to use this tool over alternatives, but the intent is obvious given the sibling set and the read-only nature. A minor gap is the lack of explicit 'when not to use' guidance, but the context is strong enough.

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

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