Skip to main content
Glama
neozhehan

Figma Edit MCP

by neozhehan
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

Create Component Set

create_component_set

Combine Figma components into a component set with property definitions (variants). Assign property values to each component to create a variant group in your design.

Instructions

Combine components into a component set (variants) with property definitions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parentIdYesID of the appendable parent container (frame, group, page, section, etc.) to place the set in; discover it with node_info
componentsYesArray of component objects
propertiesYesArray of property names (e.g. ['Size', 'State'])
parentNodeNameYesThe parent node's current exact name, passed back verbatim from `node_info`.
componentSetNameNoOptional non-empty name for the component set

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoID of the created component set
nameNoName of the component set
typeNoNode type (COMPONENT_SET)
errorNo
warningNoWarning message if some properties could not be read
parentIdNoID of the parent the set was placed into — confirm containment without a follow-up read
childCountNoNumber of variants in the set
variantPropertiesNoVariant properties definition

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed10 schema fields changedv2.3.3
    • changedInput schema / properties / componentSetName / description
      Previous value: -"Name for the component set"New value: +"Optional non-empty name for the component set"
    • addedInput schema / properties / componentSetName / minLength
      Added value: +1
    • addedInput schema / properties / components / items / additionalProperties
      Added value: +false
    • changedInput schema / properties / components / items / properties / nodeName / description
      Previous value: -"Current name (for verification)"New value: +"The component's current exact name, passed back verbatim from `node_info`."
    • changedInput schema / properties / parentId / description
      Previous value: -"Parent frame to place the set in"New value: +"ID of the appendable parent container (frame, group, page, section, etc.) to place the set in; discover it with node_info"
    • changedInput schema / properties / parentNodeName / description
      Previous value: -"Name of parent node (required if parentId provided, for verification)"New value: +"The parent node's current exact name, passed back verbatim from `node_info`."
    • changedInput schema / required
      Previous value: -[
-  "components",
-  "properties"
-]New value: +[
+  "components",
+  "properties",
+  "parentId",
+  "parentNodeName"
+]
    • addedOutput schema / properties / error
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "code": {
+      "description": "Stable machine-readable failure code (see the error playbook)",
+      "type": "string"
+    },
+    "details": {
+      "description": "Optional structured context (e.g. partialMutation, before-values)"
+    },
+    "message": {
+      "description": "Human/agent-readable message embedding its own recovery",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / parentId
      Added value: +{
+  "description": "ID of the parent the set was placed into — confirm containment without a follow-up read",
+  "type": "string"
+}
    • removedOutput schema / required
      Removed value: -[
-  "id",
-  "name"
-]
  2. Changed5 schema fields changedv2.3.2
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +{}
    • addedOutput schema / properties / childCount
      Added value: +{
+  "description": "Number of variants in the set",
+  "type": "number"
+}
    • addedOutput schema / properties / type
      Added value: +{
+  "description": "Node type (COMPONENT_SET)",
+  "type": "string"
+}
    • addedOutput schema / properties / variantProperties
      Added value: +{
+  "additionalProperties": {},
+  "description": "Variant properties definition",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / warning
      Added value: +{
+  "description": "Warning message if some properties could not be read",
+  "type": "string"
+}
  3. Changed1 schema field changedv2.3.0
    • addedInput schema / additionalProperties
      Added value: +false
  4. Changed1 schema field changedv2.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "id": {
+      "description": "ID of the created component set",
+      "type": "string"
+    },
+    "name": {
+      "description": "Name of the component set",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "name"
+  ],
+  "type": "object"
+}
  5. First observedv1.5.2

TDQS

A3.6/5.0
Behavior2/5

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

Annotations include only openWorldHint: true, which does not capture safety or side effects. The description states 'Combine components into a component set' but does not disclose that the operation may mutate the source components, alter their parent container, or require specific permissions. This leaves the agent without critical behavioral context for a create/mutation operation.

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 a single concise sentence of 11 words that captures the core action and key distinguishing detail. No unnecessary words; structurally ideal.

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?

Given the complete parameter schema, existing output schema, and an annotation, the description is adequate but not fully complete. It omits clarifying how propertyValues map positionally to properties (though schema hints at this) and does not explain the practical effect on the component set's parent hierarchy. However, the overall context from schema is strong.

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%, with each parameter having a descriptive comment (e.g., parentId explains it is an appendable container and references node_info). The description itself adds no additional parameter semantics, so the baseline score 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 uses the active verb 'Combine' and specifically names the resource 'component set (variants) with property definitions,' making it clear what the tool accomplishes. It differentiates from sibling tools like create_component and create_instance by its focus on combining multiple components into a set.

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 description does not explicitly mention when to use this tool versus alternatives such as create_component or component_manage_property. It implies that it is used when existing components need to be combined into a set, but provides no explicit exclusions or alternative suggestions.

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/neozhehan/figma-edit-mcp'

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