Skip to main content
Glama
the-real-talk

the-real-talk

edit_text_style

Update an existing text style by ID or name to change font, size, line height, letter spacing, and variable bindings.

Instructions

Edit an existing text style (by ID or name): font, size, line height (lineHeight {unit PIXELS|PERCENT|AUTO, value} or lineHeightPercent), letter spacing %, name, and variable bindings (fontFamily, fontWeight, fontSize, lineHeight, letterSpacing).

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

Input Schema

NameRequiredDescriptionDefault
nameNo
styleYes
fontSizeNo
fontStyleNo
fontFamilyNo
lineHeightNoLine height in pixels, percent or AUTO. Do not combine with lineHeightPercent.
fontSizeVariableNo
lineHeightPercentNo
fontFamilyVariableNo
fontWeightVariableNo
lineHeightVariableNo
letterSpacingPercentNo
letterSpacingVariableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 disclosure burden. It does reveal that the tool is a mutation of an existing object and enumerates the two mutually exclusive line-height representations, but it never states update semantics (partial vs. full replacement of unspecified fields), permission requirements, or what happens on an unknown style name.

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?

A single compact sentence that front-loads the action and resource, then enumerates editable fields with the line-height alternatives in a nested parenthetical. Nothing is padded, though the density of the field list hurts scannability slightly.

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 13-parameter mutation with no output schema and no annotations, the description covers the editable surface reasonably well. It still leaves gaps an agent needs: which fields are required, how name-based lookup conflicts are resolved, and whether omitted fields are preserved or cleared.

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 only 8% across 13 parameters, so the description must compensate, and it does name most fields (name, size, line height, letter spacing, and the five variable bindings). It is loose in places: 'font' is ambiguous between fontFamily/fontStyle/fontWeight, and the 'style' identifier parameter's exact semantics (ID vs. name resolution) are only hinted at.

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 ('Edit an existing text style') plus the identifier modes (by ID or name). It separates this from 'create_text_style' implicitly, but never distinguishes it from its near-identical siblings 'set_text_style' and 'set_text_range_style', so an agent cannot fully disambiguate from the description alone.

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?

'Edit an existing text style' implies the precondition that a style must already exist, which is useful context. However there is no explicit when-to-use guidance, no mention of when to pick this over set_text_style or set_text_range_style, and no stated behavior if the ID/name does not resolve.

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