Skip to main content
Glama

figma_create_text

Creates a text node in the open Figma file at specified x/y coordinates, with optional font, size, fill color, and parent; fails rather than substituting a different font.

Instructions

创建文本。指定字体失败不会改用其它字体。

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": {
      "characters": "<characters>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "figma_create_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
fillNo
fontNameNo
fontSizeNo
parentIdNo
charactersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description must disclose all behavioral traits. It usefully discloses one non-obvious trait: if the specified font fails, the tool does not silently fall back to another font (implying a hard failure). Beyond that, it says nothing about error behavior, default font, default fill, where the node is created when parentId is omitted, required permissions, or what the call returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and with zero filler. The size is efficient, but the brevity comes from omission rather than from disciplined editing, since critical parameter and behavior details are simply absent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter creation tool with nested objects, no annotations, and no output schema, this definition is thin. It omits required-coordinate semantics, the meaning of parentId, styling defaults, and the return value (for example, the created node id), leaving an agent unable to invoke the tool confidently beyond the three required fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 7 parameters, including two nested objects (fill with r/g/b/a and fontName with family/style), yet the description explains none of them. It only alludes to fontName via the fallback note; x, y, parentId, characters, fontSize, and fill are entirely undocumented. The description does not compensate for the coverage gap.

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 concrete verb and resource ('创建文本' / create text) and is clearly distinguishable from the geometry-creation siblings (create_ellipse, create_frame, create_rectangle). It stops short of naming a sibling or scoping the case where text should be created versus edited with figma_set_text_style, so it lacks true differentiation, but the purpose is unambiguous.

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?

There is no guidance about when to use this tool rather than a sibling, no prerequisites such as whether a frame must be selected or whether parentId is needed, and no guidance about coordinate space. An agent has to guess the context in which the call is valid.

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