Skip to main content
Glama

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
NameRequiredDescriptionDefault
nodeIdYesThe ID of the text node to modify
letterSpacingYesLetter spacing value
unitNoUnit type (PIXELS or PERCENT)

Implementation Reference

  • 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)}`
              }
            ]
          };
        }
      }
    );
  • 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)"),
  • Part of FigmaCommand union type listing 'set_letter_spacing' as a valid command sent to Figma plugin.
    | "set_letter_spacing"
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a modification operation ('Set'), implying mutation, but doesn't address permission requirements, whether changes are reversible, error conditions, or what happens if the node isn't a text node. For a mutation tool with zero annotation coverage, this is insufficient.

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 that directly states the tool's purpose without unnecessary words. It's appropriately sized for a straightforward tool and front-loaded with the essential information.

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 and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., success confirmation, error details), behavioral constraints, or integration with sibling tools. Given the complexity of modifying Figma nodes and the rich sibling toolset, more context is needed for effective use.

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%, with clear descriptions for all three parameters (nodeId, letterSpacing, unit). The description adds no additional parameter semantics beyond what the schema already provides, such as explaining what letter spacing values are typical or how units affect rendering. 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'), making the purpose immediately understandable. However, it doesn't distinguish this tool from similar sibling tools like set_font_size or set_line_height, which follow the same pattern for different text properties.

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. It doesn't mention prerequisites (e.g., needing a text node ID), exclusions, or relationships to other text formatting tools in the sibling list, leaving the agent to infer usage context from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/agenisea/cc-fig-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server