Skip to main content
Glama

inspect

Retrieve specific properties from Figma design nodes by selecting facet buckets like layout, paint, or variables. Returns only requested data for efficient inspection.

Instructions

Read design node(s) — choose what to surface with facets.

Default (no facets) returns a skeleton: id, name, type, role, children. For anything else, list the facets you need — nothing else is included.

Facets: structure name, type, size, layout shorthand — cheap overview layout layoutMode/gap/padding/align/sizing (row/column, fill/hug, etc.) paint|fill fills + Paint.boundVariables.color (see bound tokens) stroke strokes, strokeWeight, strokeAlign, dashPattern effects shadows, blurs typography|text fontFamily, fontSize, fontWeight, lineHeight, letterSpacing appearance opacity, visible, blendMode, cornerRadius, clipsContent variables node-level boundVariables + explicitVariableModes (token bindings) all everything

Parameters: node "/" for page root, or node ID from jsx/inspect results (e.g. "100:5"). facets array of facet names listed above. depth Max tree depth (default: 5, max: 10).

Examples: inspect({node: "/"}) → page skeleton inspect({node: "100:5"}) → one-node skeleton inspect({node: "100:5", facets: ["variables"]}) → token bindings only inspect({node: "100:5", facets: ["layout", "paint"]}) → layout + fills inspect({node: "100:5", facets: ["all"]}) → full properties

Use get_screenshot for visual verification. Use describe for lint/validation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeYes"/" for page root, or node ID (e.g. "100:5").
facetsNoProperty buckets to surface. Omit for a skeleton-only response.
depthNoMax depth (default: 5, max: 10)
Behavior5/5

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

With no annotations provided, the description fully discloses behavior: it's a read-only operation that returns a skeleton or specified facets. It explains what each facet returns, parameter constraints (depth max 10), and default output. No destructive or side effects are implied, and the examples clarify usage.

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?

The description is well-organized: a one-sentence summary, default behavior, a bulleted list of facets with explanations, parameter descriptions, and a set of examples. Every sentence is informative and earns its place without redundancy or unnecessary detail.

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?

Despite no output schema, the description explains return values in detail: skeleton fields and facet contents. It covers all 3 parameters with defaults and constraints. Examples illustrate various use cases. The tool's complexity is fully addressed without gaps.

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

Parameters5/5

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

Schema description coverage is 100%, but the description adds significant value beyond the schema: it explains the node parameter format ('/' for root, node IDs), the meaning and grouping of facets (e.g., 'paint|fill' combined), and provides concrete examples that illustrate parameter combinations. The facets enum is elaborated with plain-English descriptions.

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 starts with 'Read design node(s)' — a specific verb and resource. It explains the facet system to control output granularity. The last line explicitly distinguishes from sibling tools like get_screenshot and describe, providing clear differentiation.

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

Usage Guidelines5/5

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

The description details when to use the tool (reading node properties) and explicitly recommends alternatives: 'Use get_screenshot for visual verification. Use describe for lint/validation.' It also explains default behavior versus facet usage, guiding the agent on when to supply facets.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/musepy/genable'

If you have feedback or need assistance with the MCP directory API, please join our Discord server