CC Fig MCP

Overview Schema Source Related Servers Discussions Admin

set_letter_spacing

Adjust letter spacing in Figma text nodes to control character spacing using pixel or percentage values for precise typography adjustments.

Instructions

Set the letter spacing of a text node in Figma

Input Schema

TableJSON Schema

Name	Required	Description
`nodeId`	Yes	The ID of the text node to modify
`letterSpacing`	Yes	Letter spacing value
`unit`	No	Unit type (PIXELS or PERCENT)

Implementation Reference

src/talk_to_figma_mcp/tools/text-tools.ts:266-301 (handler)

Full server.tool registration including schema, description, and handler function for the 'set_letter_spacing' MCP tool. The handler sends a 'set_letter_spacing' command to the Figma plugin via websocket and formats the response.

server.tool(
  "set_letter_spacing",
  "Set the letter spacing of a text node in Figma",
  {
    nodeId: z.string().describe("The ID of the text node to modify"),
    letterSpacing: z.number().describe("Letter spacing value"),
    unit: z.enum(["PIXELS", "PERCENT"]).optional().describe("Unit type (PIXELS or PERCENT)"),
  },
  async ({ nodeId, letterSpacing, unit }) => {
    try {
      const result = await sendCommandToFigma("set_letter_spacing", {
        nodeId,
        letterSpacing,
        unit: unit || "PIXELS"
      });
      const typedResult = result as { name: string, letterSpacing: { value: number, unit: string } };
      return {
        content: [
          {
            type: "text",
            text: `Updated letter spacing of node "${typedResult.name}" to ${typedResult.letterSpacing.value} ${typedResult.letterSpacing.unit}`
          }
        ]
      };
    } catch (error) {
      return {
        content: [
          {
            type: "text",
            text: `Error setting letter spacing: ${error instanceof Error ? error.message : String(error)}`
          }
        ]
      };
    }
  }
);

src/talk_to_figma_mcp/tools/text-tools.ts:269-272 (schema)

Zod input schema defining parameters for the set_letter_spacing tool: nodeId (string), letterSpacing (number), optional unit (PIXELS or PERCENT).

{
  nodeId: z.string().describe("The ID of the text node to modify"),
  letterSpacing: z.number().describe("Letter spacing value"),
  unit: z.enum(["PIXELS", "PERCENT"]).optional().describe("Unit type (PIXELS or PERCENT)"),

src/talk_to_figma_mcp/types/index.ts:74-74 (helper)
Part of FigmaCommand union type listing 'set_letter_spacing' as a valid command sent to Figma plugin.
```
| "set_letter_spacing"
```

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 4, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Set' implies a mutation, it doesn't specify whether this requires specific permissions, if changes are reversible, potential side effects, or error conditions. The description is minimal and lacks behavioral context beyond the basic action.

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?

The description is a single, efficient sentence with zero waste—it directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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 no annotations, no output schema, and 3 parameters, the description is incomplete. It lacks behavioral details (e.g., permissions, side effects), usage context, and any information about return values or errors. While the schema covers parameters well, the overall context for safe and effective use is insufficient.

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 the schema already documents all parameters (nodeId, letterSpacing, unit) with descriptions and enum values. The description adds no additional meaning beyond what the schema provides, such as explaining how letterSpacing values interact with units or typical ranges. Baseline 3 is appropriate when the schema does the heavy lifting.

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 clearly states the action ('Set') and target ('letter spacing of a text node in Figma'), providing a specific verb+resource combination. It distinguishes from many siblings (e.g., set_font_size, set_text_content) by specifying the exact property being modified, though it doesn't explicitly differentiate from all similar 'set_' tools in the list.

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?

The description provides no guidance on when to use this tool versus alternatives, such as other text formatting tools (e.g., set_font_size, set_line_height) or general node modification tools. It lacks context about prerequisites, constraints, or typical scenarios for applying letter spacing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server