Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_motion_styles

Lists Figma Motion animation styles and local custom styles with IDs for applying them, plus the animation playhead position; fails with MOTION_UNAVAILABLE on unsupported builds.

Instructions

Read-only Motion (Beta) catalogue: Figma animation styles and local custom animation styles, plus the animation playhead position. Every entry carries the id to pass to figma_motion_apply_style. On a Figma build without the Motion API this fails with MOTION_UNAVAILABLE; it does not return an empty catalogue that looks like a file with no styles.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "figma_motion_styles"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does well: it declares read-only semantics, discloses the MOTION_UNAVAILABLE failure on builds without the Motion API, and explicitly warns that it will not silently return an empty catalogue. It omits things like permission requirements or whether custom styles are scoped per-file, so it is informative but not exhaustive.

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?

Three compact sentences, front-loaded with the read-only scope and return contents, then the id handoff, then the failure mode. Every clause carries information an agent needs; nothing is redundant.

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?

With one optional parameter, no output schema, and no annotations, the description must explain both contents and behavior, and it does: what is returned (styles plus playhead), how to use the returned ids, and how failures manifest. Nothing essential for correct invocation is missing.

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

Parameters3/5

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

There is a single parameter with 100% schema description coverage, and the schema already explains the fileKey, its optionality when one file is connected, and how to obtain it via figma_whoami/figma_ping. The description adds no meaning beyond that, so the baseline of 3 for fully-covered schemas applies.

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 opens with a specific verb and resource ('Read-only Motion (Beta) catalogue') and enumerates exactly what is returned: Figma animation styles, local custom animation styles, and the playhead position. It is distinguishable from siblings like figma_motion_apply_style or figma_motion_remove_style because it explicitly frames itself as the catalogue/read path and mentions the id handoff for apply.

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 signals the workflow context by stating every entry carries the id to pass to figma_motion_apply_style, which tells an agent to call this before applying a style. It does not explicitly say 'use this when you need X' or name any when-not condition, so it stops short of full routing guidance.

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