Skip to main content
Glama
awdr74100

figwright

by awdr74100
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_text_properties

Configure typography and layout properties for a Figma TEXT node, covering font, size, spacing, and overflow. Automatically loads fonts and applies changes in one call.

Instructions

Set a TEXT node's typography and layout/overflow properties. Typography: fontName ({ family, style }), fontSize, lineHeight, letterSpacing, textCase, textDecoration, paragraphSpacing / paragraphIndent (px between / indenting the paragraphs the text splits into at "\n" — the write half of the same fields get_design_context reads) — these load the required fonts first. Layout/overflow: textTruncation (ellipsis), maxLines (line clamp), textAutoResize. Any field may be omitted to leave it unchanged. maxLines applies when textTruncation is ENDING. Returns { ok, nodeId }.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesTEXT node id
fontNameNoFont family + style, e.g. { family: "Inter", style: "Bold" }
fontSizeNoFont size in px
maxLinesNoMax lines before truncation; null = unlimited
textCaseNo
lineHeightNoLine height: { unit: "AUTO" } or { unit: "PIXELS" | "PERCENT", value }
letterSpacingNoLetter spacing: { unit: "PIXELS" | "PERCENT", value }
textAutoResizeNoHow the text box resizes to its content
textDecorationNo
textTruncationNoENDING truncates with an ellipsis
paragraphIndentNoFirst-line indent of each paragraph in px
paragraphSpacingNoSpace between paragraphs in px (paragraphs split at "\n")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.0
    • removedInput schema / properties / maxLines / anyOf
      Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / maxLines / type
      Added value: +[
+  "number",
+  "null"
+]
  2. Changed1 schema field changedv0.1.3
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / paragraphIndent
      Added value: +{
+  "description": "First-line indent of each paragraph in px",
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / paragraphSpacing
      Added value: +{
+  "description": "Space between paragraphs in px (paragraphs split at \"\\n\")",
+  "minimum": 0,
+  "type": "number"
+}
  4. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description goes well beyond by disclosing the font-loading side effect ('these load the required fonts first'), partial-update semantics ('Any field may be omitted to leave it unchanged'), a conditional dependency ('maxLines applies when textTruncation is ENDING'), and the return shape ('Returns { ok, nodeId }'). Failure modes for non-TEXT nodes are not covered.

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?

Purpose is front-loaded and every clause carries information (units, grouping, dependencies, return value). The single dense paragraph with em-dashes and nested parentheticals is slightly run-on but not wasteful.

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

Completeness4/5

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

For a 12-parameter mutation tool with annotations but no output schema, the description supplies the missing return value, the side-effect profile, and the typography/layout grouping. Only error/permission behavior is left unstated, which is a minor gap.

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 already 83%, so the baseline is 3, but the description adds organization and dependency semantics beyond the schema: it groups the 12 params into typography vs layout/overflow and ties maxLines to textTruncation=ENDING. The paragraphSpacing/paragraphIndent explanation largely restates the schema.

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?

States a specific verb+resource ('Set a TEXT node's typography and layout/overflow properties') and splits the operation into two named groups. It does not explicitly distinguish itself from close siblings like set_text or set_text_range, but an agent can tell what it does without opening the schema.

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

Usage Guidelines3/5

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

Usage is implied rather than stated. The note that this is 'the write half of the same fields get_design_context reads' hints at the read/write pairing, but there is no explicit when-to-use, when-not-to-use, or named alternative (set_text, set_text_range, create_text_style).

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