Morpha

set_layer_transition

Set how a layer ENTERS at the start of its on-timeline window and LEAVES at the end, instead of popping. The transition is EDGE-RELATIVE — only a length and a look are stored — so it rides the edge through every later trim, slide or clip retime. Prefer this over fade_layer / apply_preset whenever the intent is 'enters and leaves nicely': those write opacity keyframes at ABSOLUTE frames, which strand themselves the moment the edge moves, and clutter the timeline lanes. A layer created WITH a block is born carrying a short fade at each edge — whether you passed the block or the editor minted one — so check inspect_layers before adding one, rather than assuming there is none. Layers created before this default existed, and any edge cleared to "cut", carry nothing and do need setting. A layer with NO block is always-present, has no edges, and a transition on it is inert. Video clips default to a hard cut, because a hard cut between shots is the grammar of short-form video. kind "cut" clears the edge back to a hard cut. The length is a request: when the window is too short to hold both ramps they are squeezed proportionally at render time, and the stored values are left intact.

Input Schema

TableJSON Schema

Name	Required	Description
`edge`	Yes	Which edge to set. "in" is the start of the layer's window, "out" the end.
`kind`	Yes	The look. "cut" = hard edge (clears any transition). "fade" = opacity ramp. "slide" = travels in/out from a direction while fading. "pop" = scales up from 80% with an overshoot.
`curve`	No	Optional easing override (linear, easeIn, easeOut, easeInOut, outQuart, outExpo, outBack, inBack, inOutBack). Defaults suit the kind: entries decelerate in, exits accelerate away.
`frames`	No	Ramp length in frames (30 fps). Default 6. Ignored for kind "cut".
`direction`	No	For kind "slide" only. On the IN edge this is where the layer comes FROM; on the OUT edge, where it goes TO. Default "left".
`elementId`	Yes	Element id of the layer (image.<id>, video.<id>, text.<id>, shapes.<id>, or group.<id>).
`projectId`	Yes	Opaque project id (a v4 UUID, from list_projects/create_project). Selects which existing project this call mutates.

Schema Changelog

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

First observedSep 7, 2026

TDQS

A4.9/5.0

Behavior5/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It explains edge-relative behavior, the absolute-keyframe pitfall of alternatives, default fades on block-created layers, hard-cut defaults for video clips, kind 'cut' clearing behavior, and render-time proportional squeezing of ramps. These are non-obvious side effects and constraints that materially affect agent decisions.

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?

Although long, every clause earns its place: purpose first, then the core edge-relative insight, then alternatives, default conditions, edge cases, and the render-time caveat. There is no repeated schema content and no filler.

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?

For a 7-parameter mutation tool with no annotations and no output schema, this description is unusually complete. It covers purpose, selection among siblings, prerequisites, default behavior, inert cases, and a limitation at render time — everything an agent needs to decide whether and how to call it.

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 already solid. The description adds meaningful semantics beyond the schema: frames is 'a request' that can be squeezed at render time, kind 'cut' clears the edge back to a hard cut, and the edge-relative concept clarifies how parameters like direction behave on in vs out edges.

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 opens with a specific verb and resource: 'Set how a layer ENTERS at the start of its on-timeline window and LEAVES at the end.' It further differentiates itself by naming fade_layer and apply_preset and explaining the key distinction: this tool stores an edge-relative transition rather than absolute keyframes.

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 gives explicit when-to-use guidance: prefer this over fade_layer/apply_preset for 'enters and leaves nicely' intent, and check inspect_layers first because layers created with a block already have a short fade. It also clarifies that no-block layers are always-present and transitions on them are inert, which prevents incorrect invocation.

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

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

Need Help?