Skip to main content
Glama
the-real-talk

the-real-talk

export_node_as_image

Export any Figma node as PNG, JPG, SVG or PDF: return the image directly in the response or save it to an absolute path, with optional scale, background color and overwrite.

Instructions

Export a node as an image. Without savePath the image comes back in the answer (PNG, JPG) or as text (SVG). With savePath (absolute path, extension matching the format, existing folder) the file is written to disk and only its path and size come back; an existing file is refused unless overwrite is true. background (PNG only) lays the export on a solid color so a white component can be seen: '#000000', '#rrggbbaa' or 'transparent' (default, nothing added); the node itself is never changed. PDF needs savePath.

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": {
      "nodeId": "<nodeId>"
    },
    "name": "export_node_as_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNoExport scale (default 1, max 4; ignored for SVG and PDF)
formatNoExport format (default PNG)
nodeIdYesThe ID of the node to export
savePathNoAbsolute path of the file to write
overwriteNoAllow replacing an existing file at savePath
backgroundNoPNG only: 'transparent' or a hex color laid behind the image

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the two return shapes, the refusal of an existing file unless overwrite is true, the absolute-path/extension/folder requirements, and explicitly reassures that the node itself is never changed. The one gap is how the inline image is actually delivered (base64 payload, image content block, or text), which is left vague.

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?

Content is front-loaded (what it does, then the inline-vs-disk split, then format-specific caveats) and nearly every clause carries actionable constraint. It is a single dense block, though; the savePath/background clauses could be broken out for faster scanning without losing information.

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?

For a six-parameter tool with no output schema, the description covers return behavior for both modes, overwrite safety, and format-specific limits such as PDF requiring savePath. The remaining ambiguity is the exact shape of the inline image response, which matters more here precisely because no output schema exists.

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

Parameters4/5

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

Schema coverage is 100%, so a 3 is the baseline, but the description genuinely adds meaning: savePath must be absolute with a matching extension in an existing folder, overwrite governs refusal of an existing file, and background is PNG-only with default 'transparent' that adds nothing behind the image. scale is left entirely to the schema, which is fine given its documented default and max.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a specific verb and resource ('Export a node as an image') and immediately enumerates the supported formats, so an agent knows exactly what the tool produces. None of the sibling tools perform export, and the description makes that scope unambiguous without needing to name them.

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?

The description clearly branches the two usage modes: omit savePath to get the image back inline, supply savePath to write to disk, and it states the hard prerequisite that PDF requires savePath. It does not cite any alternative tool or exclusion, but no sibling performs export, so the practical guidance is complete.

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

Deploy Server

Other Tools