Skip to main content
Glama
AvYour

Figxel

by AvYour
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Set text properties

figma_set_text_properties
Idempotent

Set typography on whole Figma text nodes—font, weight, size, spacing, case, color, alignment, lists, resizing, and truncation—so AI agents can edit text styles consistently.

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

TableJSON Schema
NameRequiredDescriptionDefault
caseNo
listNoNumbered or bulleted paragraphs; none removes the list.
alignNo
colorNo
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. First observedv0.1.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare non-read-only, idempotent, non-destructive, but the description adds real behavior beyond them: per-run vs whole-node weight resolution, `fellBack` reporting for substituted fonts, ellipsis truncation via maxLines, board/table text restyling with no alignment/resizing of their own, and per-item failure isolation. That is substantive context an agent cannot derive from structured fields.

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?

Front-loaded with purpose and scope, then semantics, then the alternative and return contract. It is dense and information-rich rather than padded, though a few clauses (editor support, leading trim, wrap style) could be tightened without loss.

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?

No output schema exists, and the description compensates by documenting the return shape (`items: [{ id, ok, error? }]`) and partial-failure semantics. Combined with the alternative-tool pointer, edge cases for board/table text, and editor support, an agent has everything needed to call it correctly.

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?

With 21 params and 71% schema coverage, the schema carries most syntax (lineHeight, letterSpacing formats, enum meanings), and the description supplies the taxonomy of properties plus the weight-matching/`fellBack` nuance that the schema only hints at. It does not add format detail for the several params lacking schema descriptions (case, align, color, decoration, fontSize), so it is strong but not exhaustive.

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+resource (change typography on whole text nodes) and enumerates the covered property set, making its scope explicit. It also names the sibling it is not — figma_set_text_range for partial text — so an agent can separate the two without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit routing rule: 'For part of a text use figma_set_text_range,' and adds applicability per editor context (Design supported; FigJam/Slides unverified). This is exactly the when/when-not/alternative guidance the dimension rewards.

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