Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_motion_inspect

Read a node's Motion state—animation styles, keyframe tracks, timelines, and exposed methods—to get the ids and track shapes required before using any Motion write tools.

Instructions

Read-only Motion (Beta) state of one node: applied animation styles, manual keyframe tracks, computed animations, timelines and which node-level Motion methods this build exposes. Use it before any Motion write; the ids and track shapes it returns are the inputs to the write tools.

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_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdNoDefaults to the current single selection
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.2/5.0
Behavior4/5

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

No annotations are provided, so the description must carry the load, and it does declare read-only semantics, Beta status, and the fact that the exposed method set depends on the running build. It omits failure behavior (for example, a node with no Motion data or an unsupported build) and any performance or permission context.

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?

Two sentences, both front-loaded with the important information: the first defines the payload and the second defines when to call it. Nothing is redundant or padded.

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?

With no output schema, the description correctly compensates by enumerating the returned fields, and the prerequisites are covered. What is missing is edge-case behavior for nodes without Motion data and what happens in a build that exposes few methods, which matters for a Beta feature.

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?

Schema coverage is 100% and both parameters already document their defaults and multi-file resolution, so the baseline is 3. The description adds only the 'one node' scoping idea; it contributes no new meaning about nodeId format or fileKey selection.

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?

It names a specific verb and resource ('Read-only Motion (Beta) state of one node') and enumerates exactly what is returned: applied animation styles, manual keyframe tracks, computed animations, timelines, and exposed node-level Motion methods. That separates it cleanly from figma_inspect and from the figma_motion_* write siblings.

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?

'Use it before any Motion write; the ids and track shapes it returns are the inputs to the write tools' gives explicit sequencing and shows that it is the prerequisite for the sibling tools. It does not spell out a skip condition or name a specific alternative for non-Motion node inspection, so it falls short of a full when/when-not statement.

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