Skip to main content
Glama
the-real-talk

the-real-talk

create_text_style

Creates a local text style with font family, style, size, line height, and letter spacing; optionally binds font properties to variables and rejects duplicate names.

Instructions

Create a local text style (family, style, size, line height as lineHeight {unit PIXELS|PERCENT|AUTO, value} or lineHeightPercent, and letter spacing %), with fontFamily, fontWeight and fontSize optionally bound to variables (IDs). Refuses a name that already exists.

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": {
      "name": "<name>",
      "fontFamily": "<fontFamily>",
      "fontStyle": "<fontStyle>",
      "fontSize": "<fontSize>"
    },
    "name": "create_text_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
fontSizeYes
fontStyleYesFigma font style, e.g. Medium
fontFamilyYes
lineHeightNoLine height in pixels, percent or AUTO. Do not combine with lineHeightPercent.
fontSizeVariableNoFLOAT variable ID
lineHeightPercentNo
fontFamilyVariableNoSTRING variable ID
fontWeightVariableNoFLOAT variable ID
letterSpacingPercentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose one genuinely useful behavior: the call fails if the name already exists. It also clarifies the lineHeight representation (unit plus value) and that certain fields can be bound to variable IDs. It does not say whether the style appears in the local styles panel, whether a style ID is returned, or what permissions/scope are required for a mutation.

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

Conciseness3/5

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

The verb and resource are front-loaded, and the second sentence is tight. The first sentence is a long nested parenthetical that packs field enumerations into one breath, making it dense to parse, though each clause does carry real information.

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 10-parameter mutation tool with no annotations and no output schema, the definition covers the creation semantics and one failure mode but leaves the return value, side effects, and relationship to sibling style tools unexplained. It is adequate to attempt a call but not complete enough to predict the outcome confidently.

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?

At 50% schema coverage across 10 parameters, the description does useful work: it explains that line height can be expressed via the lineHeight object or lineHeightPercent, that letter spacing is a percentage, and that fontFamily/fontWeight/fontSize may be bound to variable IDs. However, several of these points restate schema descriptions, and fontStyle, name length limits, and the distinction between the three variable parameters remain unaddressed beyond what the schema already says.

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?

"Create a local text style" gives a specific verb and resource, and the parenthetical enumerates exactly which style properties are set (family, style, size, line height, letter spacing). Differentiation from siblings is only implied by the verb (create vs. edit); the description never names edit_text_style or explains that this creates a new style rather than mutating an existing one.

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?

There is no explicit when-to-use guidance, nor any statement of when to choose this over edit_text_style or the paint/effect style creators. The only actionable guidance is the implicit precondition in "Refuses a name that already exists," which tells the agent a unique name is required but not when this tool is the right choice.

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