Skip to main content
Glama

figma_set_text_style

Set text node styles in Figma by node ID, including font, size, line height, letter spacing, alignment, and text content.

Instructions

设置文本节点级样式。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "nodeId": "<nodeId>"
    },
    "name": "figma_set_text_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYes
fontNameNo
fontSizeNo
charactersNo
lineHeightNo
letterSpacingNo
textAlignHorizontalNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.8/5.0
Behavior1/5

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

There are no annotations, so the description carries the full behavioral burden, and it discloses nothing. It does not say whether unspecified properties are left untouched or reset, whether existing styles are overwritten, whether the node must already be a text node, or what errors occur on a non-text nodeId.

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

Conciseness2/5

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

It is a single short sentence, so there is no wasted wording, but this is under-specification rather than conciseness. For a 7-parameter mutation tool the one-liner leaves essentially everything unsaid.

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

Completeness1/5

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

With 7 parameters (nested objects included), zero schema descriptions, no annotations, and no output schema, the description should carry far more. It provides no parameter guidance, no mutation semantics, and no return information, making it inadequate for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 7 parameters, several of them nested objects (fontName, lineHeight, letterSpacing), and the description explains none of them. It never mentions nodeId, characters, fontSize, or the unit enums, so an agent gets no meaning beyond raw type constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"设置文本节点级样式" gives a verb (设置/set) and a resource (文本节点级样式/text node-level style), so the general purpose is identifiable. However, "节点级样式" is vague about which text properties are being set, and nothing distinguishes it from sibling style tools like figma_set_fill or figma_set_effects. It sits at minimum-viable clarity.

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

Usage Guidelines2/5

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

The description contains no when-to-use guidance, no prerequisites, and no mention of alternatives among the many sibling set_* tools. An agent must infer from the name alone that this applies to existing text nodes rather than creating one (figma_create_text).

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