Skip to main content
Glama
the-real-talk

the-real-talk

set_text_style

Apply an existing local text style to a Figma text node by specifying its style ID or exact style name, keeping text consistent with your design system.

Instructions

Apply an existing local text style to a text node. The style is designated by its ID or its name.

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>",
      "style": "<style>"
    },
    "name": "set_text_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleYesText style ID (S:...) or exact style name
nodeIdYesID of the text node

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 disclosure burden. It says nothing about what happens to existing style overrides on the node, whether all characters of the node are affected or only a range, whether it requires edit permission, or whether it fails on library (non-local) styles beyond the word 'local'.

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?

Two short sentences, front-loaded with the action and target. The second sentence largely repeats what the schema already documents about the style parameter, so it earns its place only marginally.

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 a two-parameter mutation tool with no annotations and no output schema, the definition covers the happy path but omits effect on existing overrides, return value, and error behavior. Adequate to invoke, thin on consequences.

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 coverage is 100% and the schema description already states 'Text style ID (S:...) or exact style name', which the description merely restates. It adds no format details, no failure semantics for an unresolvable name, and no clarification of how name collisions are handled.

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?

The description gives a specific verb ('Apply') and resource ('an existing local text style') plus the target ('a text node'), which is enough to distinguish it from create_text_style or edit_text_style. It stops short of naming siblings such as apply_style or set_text_range_style, so sibling differentiation is only implied.

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 word 'existing' signals that a style must already exist, implying create_text_style is a prerequisite, but no when-to-use or when-not-to-use rule is stated. There is no guidance about choosing this over set_text_range_style or apply_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