Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_design_system

Export or diff a Figma file's local design system as a comparable JSON snapshot of styles, variables, and components; inventory, export, and diff are read-only.

Instructions

Export or diff the file's local design system as one comparable snapshot: paint/text/effect/grid styles, variable collections with modes and per-mode values, and components/component sets with their property definitions. "inventory" returns the snapshot; "export" writes it to a JSON file and returns the path, byte count and sha256; "diff" compares that file with the live file and reports added/removed/changed by stable key, not by name. Read-only: it never creates or changes a style, variable or component.

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

Input Schema

NameRequiredDescriptionDefault
pathNoexport: destination JSON; diff: the previous export to compare against
actionNoinventory
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.
includeNoSections to include; default all three
maxDiffNodiff: list at most this many entries per bucket
maxItemsNoSnapshot item cap; truncation is reported

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?

With no annotations, the description carries the full load and does well: it declares read-only semantics ('never creates or changes a style, variable or component'), discloses export return values (path, byte count, sha256), explains that diff keys on stable key rather than name, and notes truncation is reported. It omits permission/auth requirements and any error or failure behavior, which keeps it from a 5.

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 sentences, front-loaded with the core capability, then the three actions in quoted form, then the read-only guarantee. Every clause carries information; no restatement of the title or filler.

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 six-parameter, multi-mode tool with no output schema and no annotations, the description covers mode behavior, file selection, truncation and diff semantics. Gaps remain around the snapshot's structure, how the 'stable key' is derived, and whether library/remote assets are excluded — the word 'local' implies it but is not spelled out.

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 83%, so the schema already documents most parameters and the baseline is 3. The description adds some meaning beyond it — that path is a destination for export but the previous export for diff, and that maxDiff caps entries per bucket — but it says nothing extra about include or maxItems beyond what the schema states.

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 ('Export or diff the file's local design system as one comparable snapshot') and then enumerates exactly what the snapshot contains: paint/text/effect/grid styles, variable collections with modes and per-mode values, and components/component sets with property definitions. The three actions are named and distinguished from one another, so an agent knows this is a snapshot/export tool rather than a search or inspection tool.

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 clear per-action guidance: 'inventory' returns the snapshot, 'export' writes a JSON file and returns path/bytes/sha256, 'diff' compares that file against the live file. It also states the prerequisite for fileKey ('required once more than one file is connected; figma_ping lists them'). It stops short of naming a sibling alternative for read-only browsing, so 4 rather than 5.

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