Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_motion_set_keyframes

Create or update a manual Motion keyframe track on a Figma node for properties, paints, strokes, or effect fields; dry-run by default, then apply with verification and rollback on mismatch.

Instructions

Set one manual keyframe track on a node (Motion Beta): a property such as OPACITY/TRANSLATION_X/SCALE_XY, a paint/stroke, or an effect field. The track carries baseValue and keyframes with timelinePosition in seconds; positions must be unique and all values in one track must share a type. dryRun defaults to TRUE; apply re-reads and verifies every keyframe's position, value and easing, then rolls back on any mismatch. This writes Motion data; it never fabricates a local animation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "field": "<field>",
      "track": "<track>"
    },
    "name": "figma_motion_set_keyframes"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldYes
trackYes
dryRunNoTRUE (default): plan only, no document write. FALSE: apply in one undo transaction.
nodeIdNoDefaults to the current single selection
planIdNoThe planId returned by the dry run. Apply is refused if the arguments or the node's Motion state changed.
fileKeyNoWhich connected Figma file to use: its fileKey (figma_whoami) or, when omitted, the only connected file. Required once more than one file is connected; figma_ping lists them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.36.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full disclosure burden and does: it names the default that prevents writes (dryRun=TRUE), says apply runs in one undo transaction and rolls back on any position/value/easing mismatch, and states it never fabricates a local animation. The type-uniformity and unique-position constraints are also pre-emptive behavioral warnings.

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 action, then the data shape, then the safety behavior — the right ordering. The three sentences are dense but each earns its place; the parenthetical enum lists are slightly heavy in prose form.

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 six-parameter nested-schema mutation tool with no output schema, the description covers the action, the value model, the safety contract, and the dry-run-to-apply handshake. An agent has everything needed to invoke it correctly without guessing about destructive side effects.

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?

Beyond the 67%-covered schema, it explains that baseValue and keyframes form one track, that timelinePosition is in seconds, and that positions must be unique while all values share a type — meaning the schema alone does not. It adds little on nodeId, planId or fileKey, but those already have descriptive schema text, so the gap is minor.

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?

"Set one manual keyframe track on a node" gives a specific verb and resource, then enumerates the accepted field families (PROPERTY, paint/stroke, effect field). That precision separates it from figma_motion_remove_keyframes, figma_motion_apply_style and figma_motion_inspect without the agent needing to open any schema.

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 states the two-phase workflow clearly: dryRun defaults to TRUE (plan only), and apply requires the planId from that dry run and is refused if arguments or Motion state changed. What is missing is an explicit statement of when to reach for this tool versus figma_motion_apply_style or a sibling track tool, so the routing is inferred rather than spelled out.

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