Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_download_assets

Export selected Figma nodes to PNG, JPG, SVG, or PDF files on disk, with configurable scale and output directory, then return the saved file paths.

Instructions

Export nodes to files on disk (PNG/JPG/SVG/PDF) and return the paths.

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": {
      "nodeIds": "<nodeIds>"
    },
    "name": "figma_download_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNo
formatNoPNG
outDirNoDefaults to a temp directory
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.
nodeIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.36.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. It discloses the key side effect (writes files to disk, returns paths), but says nothing about overwrite behavior, file naming, permission/auth needs, partial failures, or the 50-node cap.

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 sentence with zero filler, and the primary purpose plus the return shape are front-loaded. It is efficient rather than padded, though it is terse to the point of omitting useful context.

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

Completeness2/5

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

Five parameters, no annotations, no output schema, and only 40% schema description coverage. The one sentence cannot cover the fileKey selection rules, scale bounds, node-count limit, or output-path semantics that an agent needs to invoke this correctly.

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 40%, below the threshold where the schema can do all the work. The description only echoes the format enum already in the schema and adds nothing about scale, nodeIds format, or outDir semantics that would compensate for the undocumented parameters.

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 ('Export'), resource ('nodes'), target ('files on disk'), supported formats, and the outcome ('return the paths'). An agent can tell it produces file artifacts rather than inline images, though it never distinguishes itself from similarly-named siblings like figma_get_screenshot or the figma_export_* family.

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 when-to-use or when-not-to-use guidance is given. With many export-adjacent siblings (figma_get_screenshot, figma_export_web_handoff, figma_export_9slice), an agent gets no routing help for choosing this tool over them.

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