Skip to main content
Glama
tokensqueezer-mcp

tokensqueezer-mcp

list_figma_components

Lists all components, component sets, instances, and variant states in the current Figma selection tree, including full hierarchy paths for each item.

Instructions

List all components, component sets, instances, and variant states in the current Figma selection tree with full hierarchy paths.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses the scoping constraint (current selection tree) and that results include full hierarchy paths, which is useful. It does not state that this is a read-only lookup, how results are ordered, whether the selection is required or optional, or how empty selections are handled.

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?

A single front-loaded sentence with no filler; the scope constraint and the returned entity types are packed into one clause each. Nothing is redundant or buried.

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 zero-parameter read tool with no output schema, the description covers the object types and the hierarchy-path payload, which is most of what an agent needs to decide to call it. Missing only edge-case behavior (empty selection) and result ordering, which are minor for this complexity level.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the implicit baseline would be 4. Marked down slightly because the description does not clarify that the tool is entirely selection-driven (i.e., the selection effectively substitutes for parameters), which is the one semantic point worth making for a zero-param tool.

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?

States a specific verb ('List') and enumerates the exact resource types returned: components, component sets, instances, and variant states, plus the hierarchy path detail. This is clearly distinguishable from a generic layer search like search_layers, though the description never names any sibling explicitly.

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?

The phrase 'in the current Figma selection tree' implies a prerequisite (an active selection) and scopes usage to whatever the user has selected. However, there is no statement of when to prefer this over search_layers or get_design_spec, and no note on what happens when nothing is selected.

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