Figma
Service domainDESIGN
Arcade Optimized
Arcade tools designed for LLMs to interact with Figma
33tools
Figma Toolkit
Arcade's Figma toolkit lets LLMs interact with the Figma API to read design files, manage comments, inspect libraries, and manipulate design tokens — covering the full range of Figma REST API capabilities available to an authenticated user.
Capabilities
- File & node inspection — retrieve full file structure, specific pages, individual nodes (including raw paint/style/variable data), version history, and file metadata across all editor types (Design, FigJam, Slides).
- Comments & reactions — create, reply to, delete, and react/unreact to comments; deletion is the only way to resolve a thread since Figma exposes no resolve endpoint.
- Component, style & component-set libraries — fetch published components, component sets, and styles from individual files or team libraries; retrieve metadata by key.
- Dev resources — attach, update, list, and remove links from design nodes (e.g., pointing a frame at a JIRA ticket or GitHub PR).
- Design tokens / variables — read local and published variables and collections with per-mode values; create, update, and delete variables, collections, and modes in atomic batches; export images as temporary URLs.
- Enterprise analytics — query weekly usage, insertion/detachment, and binding actions for components, styles, and variables; identify blast radius of token changes across the organization. (Requires Figma Enterprise.)
OAuth
This toolkit authenticates via OAuth 2.0 through Figma. See the Arcade Figma auth provider docs for setup details.
Available tools(33)
33 of 33 tools
Operations
Behavior
| Tool name | Description | Secrets | |
|---|---|---|---|
Add a comment to a Figma file or reply to an existing comment.
If parent_comment_id is provided, creates a reply to that comment.
Otherwise creates a new comment (optionally attached to a node). | |||
React to a comment in a Figma file.
Reactions are how a thread gets triaged, since Figma exposes no way to resolve one. | |||
Attach links to nodes in a Figma file.
Figma accepts each link independently, so some may be created while others are
rejected. Both outcomes are reported. | |||
Delete a comment from a Figma file.
Deleting a top-level comment also removes its replies. Figma has no way to resolve a
thread, so deletion is how a finished thread is cleared. | |||
Remove your reaction from a comment in a Figma file. | |||
Remove a link from a node in a Figma file.
The link is gone once removed. The node and its design content are untouched. | |||
Export Figma frames/nodes as images.
Returns temporary URLs to download images. URLs valid for approximately 14 days. | |||
Get comments on a Figma file.
Returns comments with pagination support. | |||
Get metadata for a specific component by its key. | |||
Get how a Figma library's components were inserted and detached, week by week.
Detachments are the signal that a component is not serving its consumers. Requires a
Figma Enterprise organization. | |||
Get published components from a file or team library.
For file: Returns all published components in the file.
For team: Returns paginated list of components across team library. | |||
Get metadata for a specific component set by its key.
A component set is a group of related component variants. | |||
Get published component sets (groups of component variants) from a file or team library.
Component sets are groups of related component variants, like a Button
with states: default, hover, pressed, disabled.
For file: Returns all published component sets in the file.
For team: Returns paginated list of component sets across team library. | |||
Get which files and teams currently use a Figma library's components.
Grouping by asset answers "how widely is this component used"; grouping by file
answers "which files depend on this library". Requires a Figma Enterprise organization. | |||
Get the links attached to nodes in a Figma file.
Dev resources point from a design node at the code, ticket, or document that
implements it. | |||
Get a Figma file's structure including pages and metadata.
Returns the file name, version, thumbnail, and list of pages.
Use depth parameter to limit how much of the tree is returned for large files. | |||
Identify a Figma file: its name, editor type, owner, and last edit.
Works for every editor type, including Slides and FigJam. The content_readable field
reports whether the file's document tree can be read at all. | |||
Get specific nodes from a Figma file by their IDs.
Returns the requested nodes with their properties and optionally their children.
Use this to fetch specific parts of a file without loading the entire document.
Set include_raw_data=True to get raw paint/style details including fills, effects,
boundVariables, and other node properties needed for inspecting gradients, styles,
and state tokens. | |||
Get a Figma file's version history, newest first.
Returns the named checkpoints and autosaves Figma retains for the file, with who
saved each one. | |||
Get the design tokens a Figma file defines or subscribes to.
Returns each variable with its value per mode, and the collections that group them.
Requires a Figma Enterprise organization. | |||
Get a list of pages in a Figma file.
Returns page IDs and names without the full node tree. | |||
Get all files in a Figma project.
Files are Figma design documents containing pages and frames. | |||
Get the design tokens a Figma library publishes to the files that subscribe to it.
This is the canonical set other files consume, as opposed to what one file defines
locally. Requires a Figma Enterprise organization. | |||
Get metadata for a specific style by its key. | |||
Get how a Figma library's styles were applied and detached, week by week.
Requires a Figma Enterprise organization. |
Page 1 of 2(25 of 33)
Last updated on