Skip to main content
Glama
Sign In
Talk to Figma MCP

Talk to Figma MCP

by kctw-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

scan_instance_keys

Scan instances under a node and retrieve deduplicated main component keys to discover published library components.

Instructions

Scan all instances under a node and return their mainComponent keys (deduplicated). Use to discover published library component keys.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scan_instance_keys"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdNoThe node ID to scan (defaults to current page)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses deduplication and that it returns mainComponent keys, but lacks details on side effects, read-only nature, or performance constraints. Adequate but not comprehensive.

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 two sentences, front-loaded with the action, and contains no extraneous words. Every sentence adds value.

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?

Given the tool's simplicity (one optional parameter, no output schema), the description fully covers the purpose, behavior, and use case. No additional information is needed.

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

Parameters3/5

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

Schema description coverage is 100% for the single parameter 'nodeId', and the description does not add any semantic meaning beyond what the schema already provides. Baseline of 3 applies.

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 clearly states the action (scan), resource (instances under a node), and outcome (return deduplicated mainComponent keys). It distinguishes from sibling tools like get_instance_info by focusing on discovery of library component keys.

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?

The description provides a clear use case ('Use to discover published library component keys') but does not explicitly mention when not to use this tool or list alternatives. The context is clear, so it earns a 4.

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