Skip to main content
Glama
Sign In
LeoGCode

figma-reader-mcp

by LeoGCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

figma_get_text

Read-only

Extract all text under a Figma node or file in reading order, with node IDs; instance overrides are included and hidden layers excluded by default.

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. Without page, or a node_id other than the document's own (0:0), it reads every page but exclude_pages (never the project's excludePages) and shares limit between them, so one cannot crowd out the rest; byPage gives each page's returned and total: pass page for one cut short. Dated by exportedAt and account, or fileModifiedAt for a file read from disk, as the server's instructions say (figma-reader help on the command line).

Input Schema

NameRequiredDescriptionDefault
fileYesA local .fig path, a Figma file key or a figma.com/design/... URL (see the server's instructions, or figma-reader help)
pageNoOnly text on this page, by name
limitNoDefault 500
fieldsNoKeys to keep in each item, of id, name, text, via, component, variant, frame (default all)
node_idNoOnly the text under this node, like 12:34 (or 12-34); the document's own id (0:0) is the whole file
refreshNoExport the live file again rather than read a local or cached copy (see the server's instructions, or figma-reader help)
exclude_pagesNoPages to leave out, by name (default none)
include_hiddenNoInclude layers hidden in the design (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.4.2
    • addedInput schema / properties / exclude_pages
      Added value: +{
+  "description": "Pages to leave out, by name (default none)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Keys to keep in each item, of id, name, text, via, component, variant, frame (default all)",
+  "items": {
+    "enum": [
+      "id",
+      "name",
+      "text",
+      "via",
+      "component",
+      "variant",
+      "frame"
+    ],
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}
    • changedInput schema / properties / file / description
      Previous value: -"Path 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."New value: +"A local .fig path, a Figma file key or a figma.com/design/... URL (see the server's instructions, or figma-reader help)"
    • addedInput schema / properties / node_id / description
      Added value: +"Only the text under this node, like 12:34 (or 12-34); the document's own id (0:0) is the whole file"
    • addedInput schema / properties / page
      Added value: +{
+  "description": "Only text on this page, by name",
+  "type": "string"
+}
    • changedInput schema / properties / refresh / description
      Previous value: -"Skip 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."New value: +"Export the live file again rather than read a local or cached copy (see the server's instructions, or figma-reader help)"
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior5/5

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

Far exceeds the readOnlyHint/openWorldHint annotations: it discloses hidden-layer exclusion, component-instance expansion with via/component/variant tagging, truncation and unresolvedInstances semantics (including unresolvedComponentsOmitted), and how limit is shared across pages. This is unusually rich behavioral disclosure with no contradiction of the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the rest is a dense run-on wall of clauses with parenthetical asides and two deferrals to 'the server's instructions / figma-reader help'. Every fact is relevant, yet it is not scannable and would benefit from sentence breaks or bullets.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-shape burden and does so: total/truncated/unresolvedInstances, byPage returned/total, and per-item tagged fields are all described. Auth/refresh prerequisites are only gestured at via 'the server's instructions', which keeps it from a 5.

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 coverage is 100%, so the baseline is 3, but the description genuinely adds meaning: exclude_pages is explicitly 'never the project's excludePages', limit is shared between pages so 'one cannot crowd out the rest', and the fields keys map to the per-item output. It stops short of explaining refresh/date semantics fully, deferring to 'the server's instructions'.

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?

The opening clause states a specific verb+resource+scope: 'All text content under a node (or the whole file) in reading order, with node ids.' That is enough to separate it from figma_get_tree or figma_get_node, though it never names a sibling as the alternative, so it falls short of a 5.

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?

It spells out how the scoping parameters behave (page vs node_id vs whole file, exclude_pages handling) but never says when to reach for this tool rather than figma_search, figma_locate or figma_get_node for the same question. Usage is implied by the scoping rules rather than stated as guidance.

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