Local Figma MCP

figma_import

Import a Figma design or prototype URL to save a local snapshot, screen PNGs, and image fills; returns a job ID for status polling.

Instructions

Import a Figma Design or prototype URL and save a local snapshot, screen PNGs and image fills. Returns a job ID; poll figma_job_status. refresh explicitly contacts Figma again.

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": {
      "url": "<url>"
    },
    "name": "figma_import"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes
`refresh`	No
`exportScreens`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds useful context: it writes local files (snapshot, PNGs, image fills), is asynchronous via a job ID, and refresh forces a re-fetch from Figma, which explains the non-idempotency. It does not mention auth requirements, failure modes, or whether existing snapshots are overwritten.

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 short sentences, front-loaded with the action and outputs, then the async follow-up, then the refresh caveat. No filler or redundancy.

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 states what is returned (job ID) and what is persisted (snapshot, PNGs, image fills), and points to the polling tool. The only meaningful gap is the unexplained exportScreens parameter, which affects whether screenshots are generated.

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 description coverage is 0%, so the description must carry parameter meaning. It explains refresh well ('explicitly contacts Figma again') and implies url's role, but exportScreens is never mentioned despite defaulting to true and controlling whether PNGs are produced. Partial compensation only.

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 gives a specific verb and resource ('Import a Figma Design or prototype URL') plus the concrete artifacts produced (local snapshot, screen PNGs, image fills), which is far more than a restatement of the name. It also names the follow-up sibling figma_job_status, though it does not distinguish itself from other siblings like figma_connect or figma_list_snapshots.

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?

It clearly states the post-call workflow ('Returns a job ID; poll figma_job_status') and clarifies the refresh flag's effect ('explicitly contacts Figma again'). There is no explicit when-not guidance or comparison against alternative import/connect tools, so it stops short of a 5.

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