Skip to main content
Glama
the-real-talk

the-real-talk

set_text_range_style

Style a selected range of a Figma text node—font family, size, case, decoration, hyperlink, and color-variable fill—or the whole text when no start and end are given.

Instructions

Style part of a text (start to end, default the whole text): text style, font family/style, size, decoration, case, fill bound to a COLOR variable, hyperlink URL.

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": "set_text_range_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
startNo
nodeIdYes
fontSizeNo
textCaseNo
fontStyleNo
hyperlinkNo
textStyleNo
fontFamilyNo
fillVariableNo
textDecorationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It is a mutation tool that overwrites existing style properties on a range, yet the description never says changes are destructive to prior values, what gets replaced versus merged, or that nodeId is required. Listing the style facets hints at scope but discloses no mutation or side-effect behavior.

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?

One compact sentence that front-loads the action and the range semantics before enumerating styleable facets. No filler, though the colon-and-comma list is dense and could be marginally more scannable.

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

Completeness3/5

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

For an 11-parameter mutation tool with no annotations and no output schema, the description covers most style facets but omits the required nodeId, range-index semantics, and any statement of effect or return. It is adequate to attempt a call but leaves real gaps around targeting and range behavior.

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

Parameters3/5

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

Schema description coverage is 0% across 11 parameters, so the description must compensate and it partially does: it maps font family/style, size, decoration, case, hyperlink URL, and clarifies that fillVariable binds a fill to a COLOR variable. However, it never mentions the required nodeId, does not say whether end is inclusive or exclusive or that end has a minimum of 1, and gives no index basis for start/end offsets or meanings for the enum values.

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 and resource ('Style part of a text') plus the selectable range ('start to end, default the whole text'), which is the key distinguishing behavior. It does not explicitly distinguish itself from set_text_style or apply_style, so it stops short of a 5.

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 parenthetical 'default the whole text' gives implicit guidance that omitting start/end styles the entire text node, which is useful. But there is no statement of when to use this versus set_text_style, apply_style, or create_text_style, and no prerequisites such as the node needing to be a text node.

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