Skip to main content
Glama
neozhehan

Figma Edit MCP

by neozhehan
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Create Text

create_text

Insert text into Figma designs with custom content, position, and optional font size, weight, and color, targeting a specific parent node.

Instructions

Create a text node with content and optional font size/weight/color.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesX position
yYesY position
nameNoOptional non-empty semantic layer name for the text node
textYesText content
fontSizeNoFont size, minimum 1 (default: 14)
parentIdYesParent node ID to append the text to
fontColorNoFont color in RGBA format
fontWeightNoFont weight: 100–900 in increments of 100 (default: 400)
parentNodeNameYesThe parent node's current exact name, passed back verbatim from `node_info`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoID of the created text node
nameNoName of the created text node
errorNo
parentIdNoID of the parent the node was placed into — confirm containment without a follow-up read

Schema Changelog

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

  1. Changed15 schema fields changedv2.3.3
    • addedInput schema / properties / fontColor / additionalProperties
      Added value: +false
    • changedInput schema / properties / fontSize / description
      Previous value: -"Font size (default: 14)"New value: +"Font size, minimum 1 (default: 14)"
    • addedInput schema / properties / fontSize / minimum
      Added value: +1
    • changedInput schema / properties / fontWeight / description
      Previous value: -"Font weight (e.g., 400 for Regular, 700 for Bold)"New value: +"Font weight: 100–900 in increments of 100 (default: 400)"
    • addedInput schema / properties / fontWeight / maximum
      Added value: +900
    • addedInput schema / properties / fontWeight / minimum
      Added value: +100
    • addedInput schema / properties / fontWeight / multipleOf
      Added value: +100
    • changedInput schema / properties / fontWeight / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / name / description
      Previous value: -"Semantic layer name for the text node"New value: +"Optional non-empty semantic layer name for the text node"
    • addedInput schema / properties / name / minLength
      Added value: +1
    • changedInput schema / properties / parentNodeName / description
      Previous value: -"Name of the parent node to verify against"New value: +"The parent node's current exact name, passed back verbatim from `node_info`."
    • changedInput schema / required
      Previous value: -[
-  "x",
-  "y",
-  "text",
-  "parentId"
-]New value: +[
+  "x",
+  "y",
+  "text",
+  "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 node was placed into — confirm containment without a follow-up read",
+  "type": "string"
+}
    • removedOutput schema / required
      Removed value: -[
-  "id",
-  "name"
-]
  2. Changed1 schema field changedv2.3.2
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +{}
  3. Changed1 schema field changedv2.3.0
    • addedInput schema / additionalProperties
      Added value: +false
  4. Changed2 schema fields changedv2.1.0
    • changedInput schema / properties / parentId / description
      Previous value: -"Optional parent node ID to append the text to"New value: +"Parent node ID to append the text to"
    • changedInput schema / required
      Previous value: -[
-  "x",
-  "y",
-  "text"
-]New value: +[
+  "x",
+  "y",
+  "text",
+  "parentId"
+]
  5. 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 text node",
+      "type": "string"
+    },
+    "name": {
+      "description": "Name of the created text node",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "name"
+  ],
+  "type": "object"
+}
  6. First observedv1.5.2

TDQS

B3.3/5.0
Behavior2/5

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

With only an openWorldHint annotation and no readOnly or destructive hints, the description carries the transparency burden. It simply states the action and styling options, without disclosing side effects, required parent context, or behavior on invalid input. The openWorldHint is not elaborated.

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, focused sentence that front-loads the verb and object. No wasted words, perfectly sized for the purpose.

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?

Given the tool's 9 parameters, nested fontColor object, and openWorldHint, the one-sentence description is fairly sparse. It omits mention of the parent requirement (though present in schema) and potential side effects. However, the rich schema and presence of an output schema reduce the burden, so a mid-range score is appropriate.

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 input schema has 100% coverage with descriptions for all 9 parameters. The description adds minimal value by grouping 'font size/weight/color' but doesn't introduce any parameter meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 a specific verb ('Create') and resource ('a text node') and names the key styling options (font size/weight/color). This clearly distinguishes it from sibling creation tools like create_shape or create_frame.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives such as text_set_content or text_set_style. It also omits prerequisites like obtaining parentNodeName from node_info, which is only mentioned in the schema, not in the description.

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