Skip to main content
Glama

capture_screenshot

Capture a screenshot of a specific Figma node or the entire page as PNG or SVG for visual inspection and automated analysis in design workflows.

Instructions

Capture a screenshot of a specific Figma node or the entire current page, returned as image data.

Prerequisites: Requires Figma bridge running and plugin connected. Use check_bridge_health to verify. Node IDs can be retrieved from get_selection or get_page_tree.

Returns on success: An image content block — { type: "image", data: base64 string, mimeType: "image/png" or "image/svg+xml" }. The image is returned directly in the response and can be passed to analyze_design for visual analysis.

Error behavior: Throws "Figma not connected" if plugin is not connected. Returns a bridge error if the node ID is invalid or the node is not visible.

Use this tool: to visually inspect a component or frame before/after mutations, as the first step in the self-heal loop (CREATE → SCREENSHOT → ANALYZE → FIX), or to feed a node image into analyze_design. Prefer SVG for vector components and PNG for complex frames.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdNoFigma node ID to capture (e.g. '123:456'). Omit to capture the entire current page. Obtain IDs from get_selection or get_page_tree.
formatNoExport format. PNG for raster output (default, works for all node types). SVG for vector output (best for icons and simple components).PNG
scaleNoExport scale multiplier (default 2 = @2x). Use 1 for quick inspection, 2–3 for high-quality analysis.
Behavior5/5

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

No annotations, but description fully discloses return type (image content block with base64 and mime type) and error behavior (not connected, invalid node ID). Adds context that image can be passed to analyze_design.

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?

Well-structured with clear sections (purpose, prerequisites, returns, errors, use cases). Every sentence adds value, no fluff.

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?

No output schema, but description fully explains return format. Covers prerequisites, errors, and integration with other tools. Complete for a capture tool.

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 has 100% coverage with descriptions; description reinforces and adds context: nodeId optional, format defaults to PNG, scale defaults to 2. Provides guidance on when to use each value.

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?

Description clearly states verb 'capture', resource 'screenshot of Figma node or entire page', and output format. Distinguishes from siblings like get_selection and analyze_design.

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?

Explicit prerequisites (Figma bridge, plugin connected), references check_bridge_health, get_selection, get_page_tree. Provides clear use cases (visual inspection, self-heal loop) and format preference (SVG for vector, PNG for frames).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sarveshsea/memi'

If you have feedback or need assistance with the MCP directory API, please join our Discord server