Skip to main content
Glama
Sign In
Figxel

Figxel

by AvYour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create an animatic

figma_create_animatic
Idempotent

Play a storyboard back at its planned pace: turn a figma_create_storyboard board into an animatic, a top-level frame Animatic · <title> with one plate per panel, each on screen on exactly the panel's frames, switched by frame-exact…

Instructions

Play a storyboard back at its planned pace: turn a figma_create_storyboard board into an animatic, a top-level frame Animatic · <title> with one plate per panel, each on screen on exactly the panel's frames, switched by frame-exact OPACITY cut pairs. Timing is read from the board as it is now (each duration caption), at the board's fps. A plate shows the panel's best picture: its styleframe once something is drawn in it, else its source rendered again, else its thumbnail; blank lists panels with nothing yet. dissolveFrames cross-fades out of a panel whose transition caption starts with "dissolve"; drift pushes each plate 3 %; burnIn labels plates. Every track is read back (verified, else notApplied). The result's render is the figma_export_video call; then judge the pace with figma_review_video. Plates 2–n rest at opacity 0, so figma_export_node shows panel 1. Skill: storyboard (figma_get_guide). One undo step. Editors: Design only, unverified.

Input Schema

NameRequiredDescriptionDefault
xNoDefault: right of everything on the page.
yNo
driftNoPush each plate's picture 3 % over its panel, so a held panel does not read as a freeze. Default false.
forceNoOverwrite on purpose. A write to a node someone changed after you last read it is refused (STALE); read it again and resend instead. Pass true only when the person said to overwrite their edit.
widthNoPlate width in px; the height follows the board's aspect. Default 1080 (1920 for 16:9).
burnInNo"panel" (default): each plate's number and title in its corner; "full": also its time, frames and the beat, action, camera and transition captions; "none".
pageIdNoThe page to build on, at its top level. Default: the board's page.
sessionNoOptional sessionId or file name, to pick a Figma file when more than one is connected.
storyboardIdYesThe board figma_create_storyboard returned (its storyboardId: the Storyboard / <title> frame), id or Figma link.
dissolveFramesNoFrames of cross-fade out of a panel whose transition caption starts with "dissolve". Default 0: every change is a cut.
idempotencyKeyNoCaller-owned retry key, ≤128 chars. Re-calling with the same key never executes twice: it returns the existing result, or waits for the op still in flight. Supply your own for anything large — if the MCP client times out (rather than the bridge), only a key you chose can be used to retry safely.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / force
      Added value: +{
+  "description": "Overwrite on purpose. A write to a node someone changed after you last read it is refused (STALE); read it again and resend instead. Pass true only when the person said to overwrite their edit.",
+  "type": "boolean"
+}
  2. First observedv0.1.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare the safety profile (not read-only, idempotent, non-destructive), but the description adds substantial behavioral context beyond them: one undo step, Design-only editors, plates 2–n resting at opacity 0 (so figma_export_node shows panel 1), STALE refusal via `force`, and every track read back as `verified`/`notApplied`.

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?

Front-loaded with the core transformation and every sentence carries real information, but the paragraph is dense and heavy, packing many behaviors (dissolve, drift, burnIn, verified tracks, render routing) into long clauses. Helpful, but not maximally scannable.

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 an 11-param, complex creation tool with no output schema, the description is complete: it explains what gets built, how timing is sourced, what `blank` lists, the verification readback, and the render/review follow-up. Nothing an agent needs to call it correctly appears missing.

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 high (91%) and already documents most params, but the description adds operational meaning: `dissolveFrames` applies only to panels whose transition caption starts with 'dissolve', `drift` pushes 3%, and `burnIn` semantics. It complements the schema rather than merely repeating it.

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?

States a specific verb and resource ('turn a figma_create_storyboard board into an animatic') and describes exactly what the output is: a top-level `Animatic · <title>` frame with one plate per panel. It explicitly names the sibling it builds on (figma_create_storyboard) and downstream tools, so an agent can distinguish it without reading the schema.

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?

Explicit routing: the result's `render` is the figma_export_video call, then pace is judged with figma_review_video, and the skill is storyboard (figma_get_guide). It also states the editor restriction ('Design only, unverified') and the one-undo-step caveat, covering when and how to invoke.

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