Skip to main content
Glama

Morpha

by ai.morphareels

freeze_frame

Freeze the picture at a frame: the clip is CUT there and a still of that frame is inserted between the halves, pushing everything after it later (the NLE 'frame hold'). This is how you hold a moment — play, freeze, continue. The still is an ordinary IMAGE layer showing that frame for holdFrames (default 150 = 5s at 30fps), so you resize, split, move or delete it like any other layer. image is the filename of a PNG of that frame, already uploaded to the project's assets — rendering one needs a browser, so capture and upload it first. The reply's frozenSourceFrame is the SOURCE frame that was frozen, which differs from frame on a retimed clip. frame must be strictly inside the clip.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frameYesProject-timeline frame to freeze at — must be strictly inside the clip.
imageYesFilename of an already-uploaded PNG of the frozen frame, in the project's assets.
elementIdYesvideo.<id> to freeze.
projectIdYesOpaque project id (a v4 UUID, from list_projects/create_project). Selects which existing project this call mutates.
holdFramesNoHow long the still holds, in frames. Defaults to 150 (5s at 30fps), the same default every added clip gets.

Schema Changelog

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

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The description explains the exact side effects: the clip is cut, a still is inserted, and everything after is pushed later. It also clarifies that the still becomes an ordinary image layer (resizable, splittable, etc.) and mentions the reply field 'frozenSourceFrame', providing strong transparency into the mutation.

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

Conciseness2/5

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

The description is highly repetitive, restating the same points multiple times (e.g., the cut-and-insert behavior, the image upload requirement, and the frame constraint). It could be condensed to two or three sentences without losing any information.

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?

The description covers the operation, prerequisites, parameter constraints, and even the reply field 'frozenSourceFrame'. It lacks explicit error handling or return format details, but with no output schema and the given context, it is sufficiently complete.

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?

While the schema already covers each parameter, the description adds meaningful context—e.g., the default holdFrames is 150 frames (5s at 30fps), the image must be an already-uploaded PNG, and frame must be strictly inside the clip. This enriches understanding beyond the bare schema.

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 that the tool freezes a video frame by cutting the clip and inserting a still image, pushing subsequent content later. This is a precise and unambiguous purpose that distinguishes it from sibling tools like add_image_layer or set_video_clip.

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?

It explicitly frames the use case as 'This is how you hold a moment — play, freeze, continue,' giving practical guidance. It also notes prerequisites like needing the PNG already uploaded and that the frame must be strictly inside the clip, but it does not explicitly contrast with alternative tools.

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