Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_motion_apply_style

Applies a Figma or custom motion style to a node with a dry-run plan and verified transaction, rolling back on any mismatch.

Instructions

Apply a Figma or custom animation style to a node (Motion Beta). dryRun defaults to TRUE and returns a planId plus the node's current styles/timelines. Apply with dryRun:false and that planId: the plugin re-reads the node, refuses a changed state, then verifies the applied style id, duration, offset and props by reading them back; any mismatch rolls the transaction back. A custom style accepts only timelineOffset, not duration or props.

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": {
      "styleId": "<styleId>"
    },
    "name": "figma_motion_apply_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoStyle family; usually inferred from styleId, but explicit is safer
propsNoFIGMA style only: values keyed by animation-style property
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.
styleIdYesFigma styleId or custom style id from figma_motion_styles
durationNoFIGMA style only: duration in seconds
timelineOffsetNoOffset in seconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.36.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses the plan/apply transaction, that the plugin re-reads the node, refuses a changed state, verifies style id/duration/offset/props by read-back, and rolls back on mismatch. Missing only peripheral traits such as error surface details or what happens to pre-existing styles on the node.

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 action and the dryRun/planId contract, then the verification guarantees, then the custom-style caveat. Dense but every sentence carries information; the long compound sentences with semicolons slightly reduce scannability.

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 9-parameter mutating tool with no annotations and no output schema, the description covers the safest call path, the verification/rollback semantics, and the one real parameter constraint. It leaves file resolution and style-family inference to the schema, which handles them adequately.

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, but the description adds genuine meaning beyond the schema by explaining the dryRun/planId coupling as a contract and by clarifying that a custom style accepts only timelineOffset, which the schema leaves implicit for timelineOffset.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource: 'Apply a Figma or custom animation style to a node', plus the '(Motion Beta)' scope marker. An agent can distinguish this write operation from sibling readers like figma_motion_inspect or figma_motion_styles, though it never explicitly contrasts with figma_motion_remove_style or figma_motion_set_duration.

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?

Gives a clear two-step workflow: dryRun defaults to TRUE and returns a planId, then apply with dryRun:false and that planId. It also states a usage constraint for custom styles (only timelineOffset, no duration or props). It stops short of naming alternative siblings or when-not-to-use cases.

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