Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_get_variable_defs

Read design-token variable definitions from a connected Figma file: fetch variables used by a node's subtree or all local variables as a flat name→value map with per-mode values.

Instructions

Variables (design tokens) used by a node's subtree, or all local variables when nothing is selected/given. Returns a flat name→value map plus per-mode values.

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

Input Schema

NameRequiredDescriptionDefault
nodeIdNo
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

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the return shape as a flat name-to-value map plus per-mode values and clarifies subtree versus all-local scope, but it omits permission/auth considerations, treatment of library or remote variables, and error behavior.

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?

The description is two compact sentences, front-loads the resource scope, and adds return-shape information without filler. Every sentence contributes directly to selecting and invoking the tool.

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 simple two-parameter getter with no output schema, the description covers scope, defaults, and return shape sufficiently for an agent to call it. It could be more complete about nodeId formatting and how library variables are treated, but no critical information 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?

Schema coverage is only 50%; fileKey is well documented in the schema, while nodeId has only a pattern and no description. The description adds meaning for nodeId by explaining subtree scope and the default when omitted, but it does not compensate for the missing nodeId format or connection details.

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?

The description clearly states a specific resource and scope: variables/design tokens used by a node's subtree, or all local variables when none is supplied. It does not explicitly differentiate itself from siblings such as figma_design_system or figma_get_design_context, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives implied usage through the conditional 'when nothing is selected/given' behavior, which helps an agent understand the default scope. However, it does not state when to prefer this tool over related retrieval or design-system tools, nor does it name alternatives.

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