Skip to main content
Glama
Sign In
Figxel

Figxel

by AvYour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create text

figma_create_text
Idempotent

A text node, placed into a frame by parentId. Inside a vertical auto-layout it fills the column and wraps (and follows the column's centre/right alignment unless align is given); elsewhere give width for text that should wrap — text…

Instructions

A text node, placed into a frame by parentId. Inside a vertical auto-layout it fills the column and wraps (and follows the column's centre/right alignment unless align is given); elsewhere give width for text that should wrap — text without one stays on a single line and can overflow. The font is loaded with the documented fallback chain; the result names the font used and flags fellBack: true when it is not the one requested. Editors: Design; unverified: FigJam, Slides.

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
nameNoLayer name, e.g. "Title". Default: the text itself.
alignNo
colorNoDefault #000000 (in FigJam: #1E1E1E, the board's own text colour).
forceNoOverwrite on purpose. A write to a node someone changed after you last read it is refused (STALE); read it again and resend instead. Pass true only when the person said to overwrite their edit.
widthNoFixed width in px; the text wraps inside it.
sizingNoHow it sizes, as in Figma's panel: { "horizontal": "fill" } to take the parent column's width; "hug" fits content; "fixed" keeps the number.
weightNoDefault Regular (in FigJam: Medium, the board's own default).
contentYesThe text. Newlines are allowed.
sessionNoOptional sessionId or file name, to pick a Figma file when more than one is connected.
fontSizeNo
parentIdNoDefaults to the current page (in Slides: the focused slide).
fontFamilyNoDefault Inter.
lineHeightNo"auto", px ("24" or "24px") or percent ("150%"), as in figma_set_text_properties; above 0. A unitless value is px, never a multiplier.
letterSpacingNopx ("0.5") or percent ("-1%"), as in figma_set_text_properties. A unitless value is px.
idempotencyKeyNoCaller-owned retry key, ≤128 chars. Re-calling with the same key never executes twice: it returns the existing result, or waits for the op still in flight. Supply your own for anything large — if the MCP client times out (rather than the bridge), only a key you chose can be used to retry safely.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / force
      Added value: +{
+  "description": "Overwrite on purpose. A write to a node someone changed after you last read it is refused (STALE); read it again and resend instead. Pass true only when the person said to overwrite their edit.",
+  "type": "boolean"
+}
  2. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (idempotent, non-destructive, closed-world), yet the description still adds real behavior: the documented font fallback chain and a `fellBack: true` flag in the result, plus the overflow consequence of omitting `width`. It omits the STALE-write refusal and the retry-key semantics, which live only in the parameter schema.

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

Conciseness4/5

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

Roughly three dense sentences for a 17-parameter tool, with the placement/wrapping rule front-loaded and the font-fallback note last. The parenthetical asides make individual sentences long but nearly every clause carries actionable information.

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?

For a 17-parameter mutation with a nested `sizing` object and no output schema, the description covers layout and font behavior but leaves the write-safety story (STALE refusal, `force`, `idempotencyKey`) and multi-file `session` selection entirely to the schema. It is adequate to call the tool, but not fully self-sufficient.

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 coverage is 76%, so the baseline is around 3, but the description genuinely adds meaning beyond the schema: `width` absence implies single-line overflow, `align` is conditional on auto-layout inheritance, and `parentId` defaults matter for placement context. Many of the 17 parameters (force, session, idempotencyKey, lineHeight, letterSpacing) are unmentioned, relying entirely on their schema text.

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 opening clause, 'A text node, placed into a frame by parentId', makes clear this creates a text node and where it lands, and the wrapping/alignment discussion reinforces that. However, it never uses an explicit verb, and it does not differentiate from near-siblings like figma_create_shapes_with_text, figma_set_text, or figma_create_text_style.

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?

It gives concrete conditional guidance: inside a vertical auto-layout the node fills and wraps automatically, elsewhere you should supply `width` or risk single-line overflow, and `align` overrides inherited column alignment. It also scopes environment applicability ('Editors: Design; unverified: FigJam, Slides'). It stops short of naming an alternative tool when this one is the wrong choice.

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