Morpha

set_text_background

Add or update the rounded background box behind a TEXT layer (text.) in one call — sets the backdrop fill plus the box's padding, corner radius, and optional stroke. Pass only the fields you want to change. New text layers are already text_autofit "hug", so padding alone shrink-wraps the box to the text — ideal for caption / sticker chips; set_layer_text(text_autofit:"hug") is only needed when adding a box to an OLDER layer still on "wrap". THIS IS HOW YOU BUILD A BUTTON: a button / CTA / chip / tag / pill / labelled badge is ONE text layer with a native background, never a rounded-rect shape with a text layer parked on top — padding is what sizes the box around the label, so the two can't drift apart when the text or the scale changes and the user drags one layer instead of two. The one exception: the box is NOT painted on CURVED text (a straight box behind a bent line reads as broken), so an arc-shaped chip genuinely needs a shape behind it. Pass fill null to remove the box. Text layers only; for shapes/images/video use set_layer_fill.

Input Schema

TableJSON Schema

Name	Required	Description
`fill`	No	Box fill: '#rrggbb' (promoted to solid) or a Fill object: {type:"solid",color} / {type:"linear",stops:[{pos:0..1,color}],angle?} / {type:"radial",stops:[{pos:0..1,color}],cx?,cy?,radius?} / {type:"mask",layer_id,color}. null clears the box; omit to leave the current fill.
`padding`	No	Uniform inset (canvas px) between the box edge and the text. 0 / omitted ⇒ no explicit padding.
`elementId`	Yes	text.<id>.
`projectId`	Yes	Opaque project id (a v4 UUID, from list_projects/create_project). Selects which existing project this call mutates.
`strokeColor`	No	Box outline colour as #rrggbb.
`strokeWidth`	No	Box outline width in px. 0 / omitted ⇒ no outline.
`cornerRadius`	No	Corner radius of the box in px. 0 ⇒ square corners.
`clear_animation`	No	Only meaningful when `fill` is given AND the layer's backdrop fill is animated. true = the new fill REPLACES the colour animation. Omitted / false = the call is refused rather than writing a fill the animation would hide.

Schema Changelog

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

First observedSep 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations at all, the description fully carries the behavioral burden: it states the mutation ('Add or update... in one call'), partial-update behavior, fill-null removal, and the important limitation that the box is not painted on curved text. An agent can predict side effects before calling.

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?

The description is longer than average, but it is information-dense and front-loaded with the core action before usage guidance. The button-building paragraph earns its place, though it could be tightened without losing value.

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 the 100% schema coverage, 8 parameters, and no output schema, the description plus schema give an agent everything needed to invoke correctly: target layer type, optional fields, partial update, removal, curved-text limitation, and routing to sibling tools.

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; the description adds meaning beyond the schema by explaining that padding alone shrink-wraps the box, that fill null removes it, and that only changed fields should be passed. It does not re-document every parameter, but it does not need to.

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 names a specific verb and resource: 'Add or update the rounded background box behind a TEXT layer (text.<id>)'. It also distinguishes this tool from siblings by stating that shapes/images/video should use set_layer_fill, so an agent can tell which tool applies.

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 gives explicit when-to-use guidance: padding shrink-wraps a box for caption/sticker chips, and buttons should be one text layer with a native background rather than a shape plus text. It also names alternatives (set_layer_text with text_autofit:'hug' for older wrap layers, set_layer_fill for non-text layers) and calls out the curved-text exception.

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?