Skip to main content
Glama
Sign In
OpenCode Figma MCP

OpenCode Figma MCP

by yhoyoex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

update_text_style

Update existing local text style properties to change fonts, size, spacing, and case; linked text nodes update automatically.

Instructions

Update properties of an existing local text style. Text nodes using the style update automatically.

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": {
      "styleId": "<styleId>"
    },
    "name": "update_text_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew style name
styleIdYesID of the text style (from get_styles or create_text_style)
fontSizeNoFont size in pixels
textCaseNoText case
fontStyleNoFont style name as shown in Figma, e.g. "Regular", "Medium", "Semi Bold", "Bold". Takes precedence over fontWeight
fontFamilyNoFont family (default: Inter, or the style's current family)
fontWeightNoFont weight (100-900), mapped to a font style name when fontStyle is not given
lineHeightNoLine height: number (pixels), "AUTO", or { unit: "PIXELS" | "PERCENT", value }
descriptionNoOptional style description
letterSpacingNoLetter spacing: number (pixels) or { unit: "PIXELS" | "PERCENT", value }
textDecorationNoText decoration
paragraphSpacingNoParagraph spacing in pixels

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that text nodes using the style update automatically, which is a meaningful side effect, but it does not state whether updates are partial, what happens to omitted properties, or whether the change is reversible.

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

Conciseness5/5

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

Two sentences, front-loaded with the core action, and the second sentence earns its place by explaining the automatic propagation effect. There is no filler or repetition.

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?

The schema is rich and covers all 12 parameters, and no output schema means return values need not be explained. However, for an unannotated mutation tool, the description is sparse on behavioral details such as partial-update semantics and reversibility, leaving real gaps.

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 100%, so every parameter is already documented in the schema with types, enums, and constraints. The description adds no additional parameter meaning beyond what the schema provides, making the baseline 3 appropriate.

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 states a specific verb and resource: updating an existing local text style. This clearly distinguishes it from create_text_style, apply_text_style, and delete_style, so an agent can identify the tool without opening schemas.

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 by 'existing local text style' and by the required styleId parameter, but the description never explicitly says when to use this tool versus apply_text_style or create_text_style. It gives no exclusions or prerequisite guidance beyond what the schema already suggests.

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