figma-mcp

get_variable_defs

Retrieve variable definitions from a Figma file. Optionally scope the lookup to a specific node to get only relevant variables.

Instructions

Get variable definitions from a Figma file

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": {
      "fileKey": "<fileKey>"
    },
    "name": "get_variable_defs"
  }
}

Input Schema

Name	Required	Description	Default
`nodeId`	No	Optional node ID to scope variable lookup
`fileKey`	Yes	Figma file key

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.7Aug 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only says 'Get', which implies read-only, but does not disclose what is returned, whether nodeId scopes the result, or any limitations or side effects.

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?

A single, front-loaded sentence with no filler or redundancy. It is efficient, though minimal in detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The schema fully documents parameters, but the description lacks usage context, return-value information, and sibling differentiation. For a simple getter it is serviceable, but not complete enough to fully support selection and invocation without inference.

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?

The input schema covers 100% of parameters with descriptions, including fileKey and nodeId, with patterns and optionality noted. The description adds no parameter semantics, but the schema already provides the necessary meaning.

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?

States a clear action ('Get') and a specific resource ('variable definitions') from a Figma file. The name and description align well. It does not explicitly differentiate from sibling tools like get_metadata or get_design_context, but the resource is specific enough to infer the distinction.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, and no prerequisites or exclusions are mentioned. The description only restates the function, leaving the agent to infer appropriate usage from the tool name alone.

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

Deploy Server