Skip to main content
Glama
Sign In
figma-free-mcp

figma-free-mcp

by haju-xp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_letter_spacing

Set the letter spacing of a Figma text node to a specific value, choosing between pixels or percent units.

Instructions

Set the letter spacing of a text node in Figma

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>",
      "letterSpacing": "<letterSpacing>"
    },
    "name": "set_letter_spacing"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYesThe ID of the text node to modify
letterSpacingYesLetter spacing value
unitNoUnit type (PIXELS or PERCENT)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.13

TDQS

B3/5.0
Behavior2/5

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

No annotations provided, so description must cover behavioral traits. Only states the action, missing details like side effects, constraints, or return behavior. Insufficient for a mutation tool.

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?

Single short sentence is concise but lacks structure. Could be improved by front-loading key info, though not verbose.

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

Completeness2/5

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

For a mutation tool with 3 parameters, no output schema, and no annotations, the description is too minimal. Lacks context on valid ranges, unit behavior, or return values, leaving gaps for an agent.

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 baseline is 3. Description adds no extra meaning beyond the schema; it merely restates the purpose.

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?

Clearly states the action (set), the resource (letter spacing of a text node), and the context (Figma). Distinguishes from sibling tools like set_font_size or set_line_height.

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?

No guidance on when to use this tool versus alternatives, no prerequisites, and no exclusion criteria. Fails to provide context for proper selection.

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