Skip to main content
Glama

figma_export_node

Export a Figma node directly to a local PNG, JPG, SVG, or PDF file using an absolute path, avoiding base64 transfer issues.

Instructions

导出节点到本地文件。必须提供绝对路径 outputPath。不要把图片以 base64 传回。

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>",
      "outputPath": "<outputPath>"
    },
    "name": "figma_export_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
scaleNo
formatNo
nodeIdYes
outputPathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/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 disclose important behavior: the tool writes to a local file and requires an absolute path, and the anti-base64 note reveals an interop constraint. But it omits overwrite behavior, default format/scale, and permission requirements, leaving substantial behavioral gaps for a write-to-disk operation.

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?

Three short sentences with the core purpose first and the hard constraint (absolute path) front-loaded; virtually no wasted wording. The base64 admonition is slightly informal but carries useful meaning.

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?

For a four-parameter export tool with no output schema and no annotations, the description should explain what is returned (e.g., a file path or confirmation) and how format/scale affect output. Those omissions, plus the undocumented parameters, leave the definition insufficient for confident invocation.

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 0% across four parameters, so the description must compensate. It only clarifies outputPath (must be absolute), leaving nodeId, scale, and the format enum (PNG/JPG/SVG/PDF) with no defaults or format-specific notes in either the schema or the description.

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 and resource: exporting a Figma node to a local file. This clearly separates it from read-oriented siblings like figma_get_node, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

Provides two constraints (absolute outputPath required, don't return base64 in the response), which implicitly tells the agent when this tool is appropriate versus fetching node data. However, there is no explicit when-to-use or when-not-to-use guidance relative to figma_get_node or the create_* siblings.

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