Skip to main content
Glama
the-real-talk

the-real-talk

scan_text_nodes

Scans text nodes inside a Figma node to inspect content, skips hidden layers, and returns a cursor to resume when time or node limits are reached.

Instructions

Scan the text nodes of a node (read-only, hidden nodes skipped). Time budget and paging: when the budget or maxNodes is reached the answer says PARTIAL and gives nextCursor. highlight:true restores the old orange flash (a temporary fill change, slow).

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

Input Schema

NameRequiredDescriptionDefault
cursorNonextCursor of a previous PARTIAL answer, to continue where it stopped
nodeIdYesID of the node to scan
maxNodesNoText nodes per call (default 1000)
highlightNoFlash each text node (default false)
timeBudgetMsNoTime budget of the plugin for this call in ms (default 60000, max 100000). When it is reached the answer says it is PARTIAL and gives nextCursor.
includeInstanceChildrenNoScan inside instances (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and mostly does: it declares the operation read-only, states that hidden nodes are skipped, and explains the PARTIAL + nextCursor truncation contract. The remaining gap is that 'highlight' silently mutates fills, which is disclosed as temporary but not flagged as a side effect with a revert path.

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?

Three compact sentences, front-loaded with the core verb and scope, then paging, then the one surprising parameter. No filler or restatement of the tool name.

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?

For a 6-parameter tool with full schema coverage and no output schema, the description adequately covers the non-obvious return behavior (PARTIAL and nextCursor) that the schema cannot express. It leaves instance-child traversal semantics and the highlight side effect only lightly covered.

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 baseline is 3, but the description adds real meaning beyond the schema: it ties timeBudgetMs and maxNodes to the PARTIAL/nextCursor contract and characterizes highlight as a temporary, slow fill change rather than just a flash. It says nothing extra about includeInstanceChildren or nodeId.

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 description names a specific verb and resource ('Scan the text nodes of a node') plus scope qualifiers ('read-only, hidden nodes skipped'). It does not explicitly name how it differs from the sibling scan_nodes_by_types, leaving that distinction to be inferred from 'text nodes'.

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?

Usage context is implied rather than stated: the cursor/PARTIAL discussion implies how to resume a truncated scan, and 'slow' hints that highlight should be used sparingly. There is no explicit when-to-use or when-not-to-use guidance, and no sibling alternative is named.

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