Skip to main content
Glama
the-real-talk

the-real-talk

convert_to_component

Turns an existing node, usually a frame, into a Figma component and assigns it a new ID. Use it to promote a design element into a reusable component.

Instructions

Turn an existing node (usually a frame) into a COMPONENT. The component gets a new ID.

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

Input Schema

NameRequiredDescriptionDefault
nodeIdYesID of the node

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/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 disclose a genuinely useful behavioral fact: the resulting component gets a new ID. However, it is silent on whether the original node is replaced, whether children and styles are preserved, and what permissions are needed.

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 with no filler. The core action is front-loaded, and the ID-change consequence follows immediately.

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 one-parameter mutation with no annotations or output schema, the definition covers the essentials and helpfully warns that the returned identity differs from the input. The remaining gap is what happens to the original node and its contents.

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?

With a single parameter and 100% schema description coverage, the schema already documents nodeId. The description adds only the hint that the node is usually a frame, which gives mild guidance on what kind of node ID is acceptable.

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?

The description states a clear verb and resource: convert an existing node into a COMPONENT. The parenthetical '(usually a frame)' narrows the accepted input. It does not explicitly contrast with the sibling create_component, so the agent must infer the difference between converting and creating from scratch.

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 by 'an existing node (usually a frame)': call it when you already have a node to promote. There is no explicit when-not guidance and no mention of create_component as the alternative when no node exists yet.

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