Skip to main content
Glama

set_line_height

Adjust text spacing in Figma by setting line height values for specific text nodes using pixel, percentage, or auto units.

Instructions

Set the line height of a text node in Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the text node to modify
lineHeightYesLine height value
unitNoUnit type (PIXELS, PERCENT, or AUTO)

Implementation Reference

  • The complete MCP tool registration including Zod input schema, description, and async handler function that executes the set_line_height logic by sending a WebSocket command to the Figma plugin and formatting the response.
    server.tool(
      "set_line_height",
      "Set the line height of a text node in Figma",
      {
        nodeId: z.string().describe("The ID of the text node to modify"),
        lineHeight: z.number().describe("Line height value"),
        unit: z.enum(["PIXELS", "PERCENT", "AUTO"]).optional().describe("Unit type (PIXELS, PERCENT, or AUTO)"),
      },
      async ({ nodeId, lineHeight, unit }) => {
        try {
          const result = await sendCommandToFigma("set_line_height", {
            nodeId,
            lineHeight,
            unit: unit || "PIXELS"
          });
          const typedResult = result as { name: string, lineHeight: { value: number, unit: string } };
          return {
            content: [
              {
                type: "text",
                text: `Updated line height of node "${typedResult.name}" to ${typedResult.lineHeight.value} ${typedResult.lineHeight.unit}`
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error setting line height: ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          };
        }
      }
    );
  • Type definition for FigmaCommand union including 'set_line_height' used for type safety in command sending.
    | "set_line_height"
    | "set_paragraph_spacing"
  • Calls registerTextTools which includes the set_line_height tool registration.
    registerTextTools(server);

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 full burden for behavioral disclosure. It states 'Set' implies a mutation, but doesn't clarify permissions, side effects, error conditions, or what happens if the node isn't a text node. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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, direct sentence with zero wasted words. It's front-loaded with the core action and target, making it highly efficient. Every word earns its place without redundancy or fluff.

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?

Given this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, error handling, or behavioral nuances. For a tool that modifies Figma nodes, more context is needed to use it effectively beyond the basic purpose.

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 parameter descriptions and an enum for 'unit'. The description adds no additional parameter semantics beyond what's in the schema. According to the rules, with high schema coverage (>80%), the baseline is 3 even with no param info in the description.

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 ('line height of a text node in Figma'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'set_font_size' or 'set_paragraph_spacing', but the specificity of 'line height' provides inherent distinction. This is clear but lacks explicit sibling comparison.

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 an existing text node), exclusions, or related tools for other text properties. The agent must infer usage from the tool name and parameters alone, with no explicit context.

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