Local Figma MCP

figma_get_variables

Retrieves accessible Figma variable collections, reporting missing access due to OAuth scope or plan limits.

Instructions

Fetch accessible Figma variable collections. Availability depends on OAuth scope and Figma plan; reports missing access.

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": {
      "snapshotId": "<snapshotId>"
    },
    "name": "figma_get_variables"
  }
}

Input Schema

Name	Required	Description	Default
`snapshotId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 7, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare openWorldHint=true and destructiveHint=false, but the description adds genuinely new behavior: access is gated by OAuth scope and Figma plan, and missing access is reported rather than failing silently. A tension remains unexplained: the tool is named 'Fetch' but carries readOnlyHint=false and idempotentHint=false, and the description never addresses whether the call has side effects or is repeatable.

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?

Two compact sentences with the action front-loaded and the access caveat second; nothing is wasted. The second sentence does carry a lot of compressed meaning, but on balance the text is efficient.

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?

For a single-parameter getter with no output schema, the description should explain the return shape and the role of snapshotId, and it does neither. The OAuth/plan caveat and the 'reports missing access' note partially compensate, but an agent still cannot predict what it will receive or what the parameter refers to.

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

Parameters2/5

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

Schema description coverage is 0% and the single required parameter 'snapshotId' is never mentioned in the description. It is unclear whether this reads live variables from a design file or variables stored in a saved snapshot, which is the one thing the description needed to clarify given a snapshot-scoped parameter.

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 specific verb and resource: 'Fetch accessible Figma variable collections.' An agent can tell it retrieves variable collections rather than screens, assets, or flows. However, it is not differentiated from the similar sibling 'get_variable_defs', so the agent cannot distinguish the two without opening both schemas.

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?

The prerequisite information is useful ('Availability depends on OAuth scope and Figma plan'), but this describes when the tool will succeed, not when to choose it. There is no guidance on when to use this versus get_variable_defs or when variables should be read from a snapshot instead, so usage is only implied.

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