Skip to main content
Glama
Sign In
Figxel

Figxel

by AvYour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Export / screenshot a node

figma_export_node
Read-only

Render a node so you can see it — the screenshot to compare against. No nodeId: the one selected layer. Without saveTo, PNG/JPG come back as an image (≤ 5 MB) with its bounds and pixel size, and SVG as markup; an inline PNG/JPG with no…

Instructions

Render a node so you can see it — the screenshot to compare against. No nodeId: the one selected layer. Without saveTo, PNG/JPG come back as an image (≤ 5 MB) with its bounds and pixel size, and SVG as markup; an inline PNG/JPG with no scale is held to 1024 px on its longest side (maxSize changes that; capped says it happened; scale asks for an exact size instead). With saveTo, or for PDF, or when larger than 5 MB, the file is written and its path returned. A relative saveTo lands in the export directory; other folders must be listed in BRIDGE_EXPORT_ROOTS. If format is omitted, the saveTo extension decides, else PNG. An animated frame renders at rest: see its motion with figma_export_video, then figma_review_video. final: true marks the delivery: under BRIDGE_PROCESS=strict a node of a brief needs a passing figma_sign_off newer than its last change. Skill: critique (figma_get_guide). For files a codebase ships (presets, original images), use figma_download_assets.

Input Schema

NameRequiredDescriptionDefault
finalNoThe delivery. Under BRIDGE_PROCESS=strict a node that belongs to a brief needs a passing figma_sign_off newer than its last change. Default false: a render to judge, never gated.
scaleNoExact pixel scale for PNG/JPG; bypasses the size cap.
formatNoPNG (default), JPG, SVG or PDF.
nodeIdNoThe node to render: an id ("12:34") or a Figma link. Default: the one selected layer.
saveToNoWrite to this file instead of returning the render inline.
maxSizeNoLongest side in pixels for PNG/JPG (never upscales). Default 1024 inline.
sessionNoOptional sessionId or file name, to pick a Figma file when more than one is connected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / final
      Added value: +{
+  "description": "The delivery. Under BRIDGE_PROCESS=strict a node that belongs to a brief needs a passing figma_sign_off newer than its last change. Default false: a render to judge, never gated.",
+  "type": "boolean"
+}
  2. First observedv0.1.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare a safe read, and the description adds substantial context beyond them: a 5 MB inline ceiling, a 1024 px cap on inline PNG/JPG, the `capped` flag, relative-path resolution into the export directory, the BRIDGE_EXPORT_ROOTS allowlist, and the fact that animated frames render at rest. That is exactly the kind of operational detail annotations cannot carry.

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?

Front-loaded with the purpose and the output-mode rules, and nearly every clause carries information. It is dense to the point of stacking parentheticals ('maxSize changes that; capped says it happened; scale asks for an exact size instead'), which costs some scannability.

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

Completeness5/5

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

There is no output schema, and the description compensates fully: it describes inline image returns with bounds and pixel size, SVG as markup, and file-path returns for saveTo/PDF/oversized cases. Edge cases (animated frames, strict mode, export roots) are all covered.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning not in the schema: `format` inferred from the `saveTo` extension with PNG fallback, `scale` bypassing the size cap, `maxSize` overriding the 1024 default, and the strict-mode consequence of `final: true`. These are behavioral semantics, not restatements.

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?

States a specific verb and resource ('Render a node') and frames the intent ('the screenshot to compare against'). It explicitly distinguishes itself from siblings figma_export_video, figma_review_video and figma_download_assets, so an agent can pick it without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use (compare a rendering), when-to-use-something-else (motion → figma_export_video then figma_review_video; shipped assets → figma_download_assets), and when the output mode changes (saveTo, PDF, >5 MB). It also flags the `final: true` gating condition under BRIDGE_PROCESS=strict.

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