figma-mcp

get_screenshot

Export any Figma node as a screenshot image. Supply the file key and node ID to capture a specific design element for sharing, review, or documentation.

Instructions

Get a screenshot (image export) of a Figma node

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

Input Schema

Name	Required	Description	Default
`nodeId`	Yes	Node ID to screenshot
`fileKey`	Yes	Figma file key

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.7Aug 30, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does say the result is an image export, but it omits return format, rendering behavior, access requirements, or any limitations. This is a minimal read-operation description with no extra behavioral context.

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?

The description is a single, front-loaded sentence with no filler. It communicates the core purpose efficiently and earns its place without redundant wording.

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?

For a simple two-parameter tool, the description is minimally viable, but it leaves out useful context such as the actual image format, return payload details, or any export-specific constraints. Given there is no output schema or annotations, a bit more context would make it complete.

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 description coverage is 100%, and both fileKey and nodeId have meaningful descriptions. The tool description adds little param-level value beyond clarifying that the output is an image, but the schema already provides adequate parameter semantics.

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 description clearly states a specific action ('Get') and resource ('screenshot/image export of a Figma node'). It is immediately distinguishable from sibling tools like get_metadata or get_flow_map, which serve different purposes.

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 guidance is provided on when to choose this tool over alternatives, nor are any conditions or exclusions mentioned. The description implies usage via the name, but does not explicitly say when a screenshot is the right tool versus getting node frames, metadata, or variables.

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

Deploy Server