Skip to main content
Glama
Sign In
Talk to Figma MCP

Talk to Figma MCP

by kctw-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

create_component_from_node

Convert any Figma frame or node into a reusable component using its node ID. Only works for nodes that are not already components or inside a component.

Instructions

Convert an existing Figma frame/node into a reusable Component. The node cannot already be a component or be inside a component.

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

Input Schema

NameRequiredDescriptionDefault
nodeIdYesThe ID of the node to convert to a Component

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.9/5.0
Behavior2/5

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

No annotations, so description must cover behavioral traits. Does not mention side effects (original node status), permissions, idempotency, or return value.

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?

Two short sentences, no fluff, essential information only.

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?

Adequate for a simple one-param tool with constraint, but missing behavioral details expected for a mutation with no annotations or output schema.

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 covers nodeId with simple description. The tool description adds the critical constraint, providing meaning beyond the schema.

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?

Explicitly states conversion of frame/node to component, with a clear constraint. Distinguishes from siblings like create_component_instance.

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?

Includes a key when-not-to-use condition (node cannot already be a component or inside one). Lacks explicit alternatives or broader usage context.

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