Skip to main content
Glama

Morpha

by ai.morphareels

delete_version

Permanently delete one saved version (bookmark or auto-snapshot). Accepts the version's UUID id or the v<N> shorthand. The bookmark v sequence keeps gaps — numbers never re-shuffle — so any external snippet referencing the deleted v<N> will fail to resolve afterwards. Idempotent: deleting a non-existent version is a no-op.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject whose version to delete.
versionIdYesVersion to delete. UUID `id` or `v<N>` shorthand.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description mentions the idempotent nature of deletion and the gap behavior in the v<N> sequence, which are important behavioral details. However, it does not explicitly warn about the irreversibility of the deletion, though 'permanently delete' implies it. Overall, it provides good transparency given the lack of annotations.

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 concise, with three sentences covering purpose, input formats, and behavioral notes. There is no redundant or extraneous information, and the structure is clear and direct.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple delete operation, the description covers the essential aspects: what it deletes, how to specify the version, and the idempotency. It does not mention potential error cases or side effects, but given the tool's simplicity, it is relatively complete. The lack of an output schema is acceptable as the tool likely returns a status or nothing.

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?

Both parameters (projectId and versionId) are already described in the schema. The description adds context about the v<N> shorthand and gap behavior, but these are more about tool behavior than parameter semantics. Since schema coverage is 100%, the description provides minimal additional parameter-specific value.

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 clearly states the tool's function: 'Permanently delete one saved version'. It also distinguishes the tool from siblings like rename_version, save_version, restore_version, and list_versions by focusing on deletion and the specific input formats.

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?

It explains the two acceptable input formats (UUID or v<N> shorthand), and notes that the v<N> sequence keeps gaps, which helps agents understand the behavior. It also states that deleting a non-existent version is a no-op, providing clear guidance on expected outcomes.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation3/5

The tool set has several clusters that overlap conceptually: add_keyframe/add_keyframes/set_keyframes_batch, move_band/move_layer/shift_group/set_group_window, and fade_layer/set_layer_transition/set_layer_visible all target similar actions. However, each tool's description is distinct and detailed enough for an agent to disambiguate after careful reading. The sheer volume of 95 tools still creates meaningful selection risk.

Naming Consistency4/5

Tool names overwhelmingly follow a verb_noun snake_case pattern (add_, remove_, set_, list_, rename_, create_, delete_), which is predictable and readable. Minor inconsistencies exist: plural variants like add_keyframes vs add_keyframe, mixed specificity like remove_keyframe vs remove_color_keyframe, and a few oddballs like reid_project and clip_processing_status. Overall the pattern is strong and helps navigation.

Tool Count2/5

95 tools is far beyond the well-scoped range and will overwhelm agents; even a comprehensive video editor could consolidate keyframe batch operations, overlay/track manipulations, and page/group window controls. Many tools are highly specific (reid_project, safe_zones, move_band) and place burden on the agent to pick among near-synonym verbs. While the broad domain justifies many operations, this count is excessive for a coherent tool surface.

Completeness3/5

The surface covers a broad editing lifecycle: layers, keyframes, text, captions, audio, pages, groups, versions, projects, workspaces, and collections, including batch operations. However, there is no MCP tool to render/export the final MP4 (explicitly delegated to an SDK) and no upload_video tool for bringing in a clip file, leaving major end-to-end gaps. For the stated purpose of building and editing videos, these are significant omissions that force agents to stop short of delivery.

Resources