Skip to main content
Glama

link_cels

Destructive

Merge selected frames into one shared cel so a single drawing appears on all of them, letting edits to any linked frame update every frame at once.

Instructions

Make several frames share one image, which is how a held pose is authored.

A linked cel is one image appearing on several frames: editing any of them edits all
of them, and the file stores the image once instead of once per frame. Use it for a
pose that genuinely repeats, such as the two extremes of a cycle that return to the
same drawing.

**The first listed frame's image is the one kept.** Every other listed frame loses
whatever was drawn on it and shows the first frame's image instead, which is the point
of linking and is not undoable from here, so check with `get_cel` first if the frames
differ.

To hold a pose for longer rather than to repeat a drawing, lengthen the frame instead
(`set_frame_duration`, or `apply_timing_curve`): a duration costs nothing, while a
repeated frame shifts every tag index.

Returns the layer's link groups: the frames that now share an image, in groups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
layerYes
framesYes
filenameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds essential detail: every non-first listed frame loses its drawing, the first frame's image is kept, and the change is 'not undoable from here.' It also suggests a pre-check with get_cel, which is actionable behavioral context beyond the annotation.

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 purpose, then layers in behavior, alternatives, and return values. Each paragraph earns its place, using bold text and short sections without wasted words.

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 destructive tool with no output schema and only minimal annotations, the description covers purpose, usage, behavioral consequences, alternatives, and even return values ('Returns the layer's link groups'). The main gap is that it does not document the filename and layer parameters, but otherwise it is complete enough for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for all three parameters. It adds critical meaning for 'frames' by explaining that the first listed frame's image is kept and others are overwritten, but it never defines 'filename' or 'layer', leaving two of three parameters semantically undocumented.

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 verb and resource: 'Make several frames share one image,' and explains the linked-cel concept. It distinguishes the operation from related siblings like set_frame_duration and apply_timing_curve by clarifying that linking repeats a drawing rather than holding a pose.

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 ('for a pose that genuinely repeats, such as the two extremes of a cycle') and when-not-to-use guidance ('To hold a pose for longer rather than to repeat a drawing, lengthen the frame instead'), naming the alternative tools set_frame_duration and apply_timing_curve. It also advises checking with get_cel first if frames differ.

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

Deploy Server

Other Tools