Skip to main content
Glama
LeoGCode

figma-reader-mcp

by LeoGCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

figma_get_text

Read-only

Extract all text content from Figma files or nodes in reading order, expanding component instances and tagging overrides, variants, and frames to locate missing text and clarify design data.

Instructions

All text content under a node (or the whole file) in reading order, with node ids. Component instances are expanded, so strings that only exist as instance overrides or component property values are included, each tagged with via (direct/instance) and, where they apply, its component, variant and enclosing frame. A field that does not apply is absent: text on the canvas has no component. Hidden layers are excluded unless include_hidden. The result always reports total/truncated/unresolvedInstances: a non-zero unresolvedInstances means text is missing, at that many places; unresolved lists each missing component once, with its count and some of those places, the most common first, and unresolvedComponentsOmitted counts the components past that listing. The result is dated by the copy it answers from. exportedAt is the ISO-8601 time this tool exported that snapshot through the browser: report what the design said then rather than as current, and pass refresh to export it again. For a local .fig the field is fileModifiedAt, that copy's own file time, which copying, syncing or re-downloading the file resets: the design data can be older than it says, and nothing here can date it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileYesPath to a local .fig file, or a Figma file key / figma.com/design/... URL. A node-id in the URL is used when this tool takes node_id and it is omitted; a tool that answers about the whole file ignores it. A key or URL uses a local '<name> [<key>].fig' from FIGMA_FILES_DIRS when one exists, otherwise exports through the browser.
limitNoDefault 500
node_idNo
refreshNoSkip local/cached copies and export the live file through the browser. Has no effect when file is a path to a .fig: that file is read as it is on disk and the result carries refreshIgnored; pass the key or URL to export the live file instead.
include_hiddenNoInclude layers hidden in the design (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark it read-only and open-world, but the description goes far beyond that. It discloses how component instances are expanded, that hidden layers are excluded by default, the meaning of unresolvedInstances and the snapshot timing with exportedAt and refresh. It even explains local file quirks with fileModifiedAt. This is exemplary transparency with no contradiction to annotations.

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?

The description is long but every sentence contributes critical edge-case information. It front-loads the primary purpose and then systematically covers instances, hidden layers, unresolved instances, and timing. It is not verbose for the complexity, though it could be better structured with bullet points. Overall, it earns its length.

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, so the description compensates by explaining the result fields (total/truncated/unresolvedInstances, unresolved, unresolvedComponentsOmitted) and their meanings. It also covers snapshot dating, refresh behavior, and local file caveats. For a tool with this many nuances, the description is remarkably complete.

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

Parameters4/5

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

Schema description coverage is 80% (node_id lacks a description). The description adds meaningful semantics for file (local resolution, URL handling, node_id inheritance), refresh (skip caches, no effect on .fig), and include_hidden (default false). It also indirectly clarifies node_id via the file parameter. This exceeds the schema baseline, though limit remains generic.

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 opens with 'All text content under a node (or the whole file) in reading order, with node ids', which is a specific verb and resource. It clearly distinguishes this from sibling tools like figma_get_tree or figma_get_node by focusing exclusively on text extraction and detailing instance expansion. The purpose is unambiguous and well-scoped.

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

Usage Guidelines4/5

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

While the description never explicitly names alternatives or says 'use this instead of X', it strongly implies usage by describing exactly what it returns and when. The coverage of node vs. file, hidden layers, and refresh behavior makes the appropriate use cases obvious. However, it does not explicitly state what it is NOT for or compare to siblings, so it misses the top score.

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