Skip to main content
Glama
Sign In
Figxel

Figxel

by AvYour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Set text properties

figma_set_text_properties
Idempotent

Change typography on whole text nodes, like Figma's text panel: font family, weight, size, line height, letter spacing, case, decoration, colour, paragraph spacing and indent, lists, alignment (horizontal and vertical), resizing…

Instructions

Change typography on whole text nodes, like Figma's text panel: font family, weight, size, line height, letter spacing, case, decoration, colour, paragraph spacing and indent, lists, alignment (horizontal and vertical), resizing, truncation, leading trim, wrap style. A new family keeps each run's own weight (a bold word stays bold); a new weight applies to all of it. A weight the family names differently ("SemiBold" vs "Semi Bold") is matched, and anything substituted is reported as fellBack. maxLines ends the text in an ellipsis after that many lines. On a board a sticky, shape or connector restyles its text, and a table every cell; those texts have no alignment, resizing or truncation of their own. For part of a text use figma_set_text_range. Returns per-item results: items: [{ id, ok, error? }] — one node failing does not fail the call. Editors: Design; unverified: FigJam, Slides.

Input Schema

NameRequiredDescriptionDefault
caseNo
listNoNumbered or bulleted paragraphs; none removes the list.
alignNo
colorNo
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.
weightNoFont weight as a number ("600") or a Figma style name ("Semi Bold" — Inter uses spaces, not "SemiBold").
nodeIdsYes
sessionNoOptional sessionId or file name, to pick a Figma file when more than one is connected.
fontSizeNo
maxLinesNoTruncate with an ellipsis after this many lines.
truncateNoTurn ellipsis truncation on or off.
wrapStyleNoFigma's textWrapStyle.
autoResizeNohug = one line that grows; wrap = fixed width, grows down; truncate = a fixed box ending in an ellipsis.
decorationNo
fontFamilyNoA family available in this Figma (figma_suggest_fonts lists ranked ones).
lineHeightNo"auto", px ("24"), or percent ("150%").
leadingTrimNocap-height removes the vertical space above and below the glyphs.
alignVerticalNoWhere the text sits in a box taller than it.
letterSpacingNopx ("0.5") or percent ("-1%").
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.
paragraphIndentNopx the first line of each paragraph is offset from the left.
paragraphSpacingNoVertical px between paragraphs.

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

A4.6/5.0
Behavior5/5

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

Annotations already declare non-readOnly, idempotent, non-destructive, closed-world, but the description adds substantial behavioral detail beyond them: per-run weight preservation vs whole-range weight application, font-name normalization with substitutions reported as `fellBack`, maxLines ellipsis semantics, board-wide restyling of sticky/shape/connector text and every table cell, and per-item partial-failure results. The STALE/force semantics are covered in the schema, completing the mutation-safety picture.

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?

The opening sentence front-loads the core purpose and the property enumeration earns its place as a capability list. A couple of sentences are dense (the font-family/weight matching explanation), but none are filler; the return-shape and editor-availability sentences are compact and useful.

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

Completeness5/5

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

There is no output schema, so the description compensates by specifying the return shape (`items: [{ id, ok, error? }]`) and the partial-failure guarantee. Combined with board behavior, weight/fellBack semantics, and editor support, an agent has everything needed to invoke this correctly on a complex 22-parameter mutation tool.

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 73% with eight enums already self-documenting, so the baseline is solid. The description adds real meaning beyond the schema by explaining weight-matching behavior and `fellBack` reporting, and by spelling out that `autoResize`/'truncate'/'maxLines' interact (ellipsis after N lines). A few parameters (color, case, decoration) still rely entirely on the schema, keeping this from a 5.

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?

States a specific verb and resource ('Change typography on whole text nodes') and immediately anchors it to a familiar model ('like Figma's text panel'), then enumerates exactly which properties are covered. It also names the sibling it is not (figma_set_text_range) and describes how it behaves differently on boards, so an agent can distinguish it from other text-mutation tools without opening a schema.

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?

Explicitly routes partial-text work to figma_set_text_range and clarifies the board/table special cases where per-node properties don't apply. It also states editor availability (Design supported; FigJam/Slides unverified). It does not contrast with related alternatives like figma_set_text (content) or figma_apply_style_to_node (applying a text style), leaving that inference to the agent.

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