Skip to main content
Glama
Figma Local Bridge

Figma Local Bridge

by Miart

figma_get_screenshot

Render a selected Figma node as PNG, JPG, or SVG to capture screenshots or export assets from the open connected file.

Instructions

Render a node as PNG/JPG (returned as an image) or SVG (returned as text).

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

Input Schema

NameRequiredDescriptionDefault
scaleNo
formatNoPNG
nodeIdNoDefaults to the single selected node
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

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose a genuinely useful behavioral trait: PNG/JPG come back as an image payload while SVG comes back as text, which affects how the result must be handled. It says nothing about permissions, size/scale limits, or failure modes on unrenderable nodes.

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?

One sentence, front-loaded with the action and resource, and the format/return-type mapping is packed into a compact parenthetical. Nothing is wasted.

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?

With no output schema and no annotations, the description correctly explains the return shape, which is the most important gap to fill. However, it omits selection/routing context (that nodeId defaults to the current selection, and fileKey is required with multiple files) that the schema states only for some parameters, leaving the definition thin for a four-parameter tool.

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 50% — nodeId and fileKey are documented in the schema, while scale and format are not. The description partially compensates by naming the three formats and tying them to return types, but adds nothing about the scale parameter's effect. Baseline 3 is appropriate given the schema does much of the work.

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?

Uses a specific verb ("Render") plus resource ("a node") and enumerates the output formats, so the agent knows exactly what it gets back. It does not differentiate itself from plausible siblings like figma_download_assets or figma_get_design_context, which also produce visual artifacts.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The agent must infer from the format list alone whether to reach for this tool versus an export or design-context sibling.

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