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);
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 a mutation action ('Set') but doesn't mention permissions, side effects, error conditions, or response format. This is inadequate for a mutation tool without annotation support.

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 wasted words. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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 insufficient. It doesn't explain what happens on success/failure, return values, or error handling, leaving significant gaps in understanding the tool's behavior.

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 fully documents all parameters (nodeId, lineHeight, unit). The description adds no additional meaning beyond implying these parameters exist, meeting the baseline for high schema coverage.

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'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like set_font_size or set_paragraph_spacing, which share similar patterns for text node modifications.

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 is provided on when to use this tool versus alternatives. The description lacks context about prerequisites (e.g., needing a valid text node ID) or exclusions (e.g., not applicable to non-text nodes), leaving usage entirely implicit.

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