Skip to main content
Glama

set_text_properties

Set typography (font, size, line height, letter spacing, text case, decoration) and layout/overflow (truncation, max lines, auto resize) for a TEXT node.

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")
Behavior4/5

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

Annotations are readOnlyHint=false and destructiveHint=false. The description adds that loading required fonts occurs, which is a side effect, and specifies the return value { ok, nodeId }. No contradictions.

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 description is well-structured with clear categories, though slightly long. It front-loads the main action and then details groups.

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?

With 12 parameters and no output schema, the description covers both property groups, explains dependencies, and states the return format. Adequate for a 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 83%, but the description adds value by categorizing parameters (typography vs layout/overflow) and explaining dependencies like maxLines relative to textTruncation, beyond the schema.

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?

The description clearly states it sets a TEXT node's typography and layout/overflow properties, listing specific fields. It distinguishes from siblings like set_text (content) and create_text (creation).

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?

The description implicitly indicates usage via listing properties, but lacks explicit guidance on when to use this tool versus alternatives or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/awdr74100/figwright'

If you have feedback or need assistance with the MCP directory API, please join our Discord server