Skip to main content
Glama
the-real-talk

the-real-talk

get_node_raw

Read raw Figma plugin-API properties of a node, including fills with bound variables, effects, layout, grids, and component data. Restrict results by depth and keys for targeted inspection.

Instructions

Read the raw Figma plugin-API properties of a node (fills with bound variables, effects, layout, min/max, constraints, grids, style IDs, characters, component properties, reactions...). depth = levels of children (default 0). keys = restrict to some properties.

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": "get_node_raw"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysNo
depthNo
nodeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does usefully disclose that this is a read operation and that depth defaults to 0 meaning no children are traversed unless requested, which prevents accidental large payloads. It says nothing about failure modes for invalid nodeIds, response size at deep depth, or whether restricted keys affect variable resolution.

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?

Three short sentences, front-loaded with the purpose, then the two non-obvious parameters. The parenthetical field list is long but each item is a real capability of the tool, so it earns its space; only minor tightening (e.g. trailing "...") is possible.

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

Completeness3/5

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

With no output schema and no annotations, the description should do more than list field families – it should indicate roughly what the returned structure looks like or how large it can get at higher depth. For a 3-parameter read tool the core is covered, but an agent still cannot predict the response envelope or error behavior.

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 0%, so the description must compensate, and it does for two of three parameters: depth is defined as levels of children with its default 0, and keys is defined as a property restriction, which is meaningfully more than the bare types in the schema. It omits the bounds (depth max 10, keys max 60) and does not describe nodeId beyond the obvious, so it falls short of full coverage.

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?

States a specific verb and resource ("Read the raw Figma plugin-API properties of a node") and immediately enumerates the property families returned (fills with bound variables, effects, layout, constraints, characters, reactions). The word "raw" plus the plugin-API framing is what separates it from the sibling get_node_info, so an agent can choose between them without opening either schema.

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 is implied rather than stated: the enumeration of raw plugin-API fields signals "use this when you need the underlying API shape rather than a summary." There is no explicit when-to-use, when-not-to-use, or named alternative (get_node_info), and no cost/size warning about raising depth.

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