Skip to main content
Glama

set_axis_align

Adjust alignment for auto-layout frames in Figma by setting primary and counter axis positioning to control element arrangement.

Instructions

Set primary and counter axis alignment for an auto-layout frame in Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the frame to modify
primaryAxisAlignItemsNoPrimary axis alignment (MIN/MAX = left/right in horizontal, top/bottom in vertical). Note: When set to SPACE_BETWEEN, itemSpacing will be ignored as children will be evenly spaced.
counterAxisAlignItemsNoCounter axis alignment (MIN/MAX = top/bottom in horizontal, left/right in vertical)

Implementation Reference

  • The handler function for the 'set_axis_align' tool. It sends the corresponding command to the Figma plugin via sendCommandToFigma with the nodeId, primaryAxisAlignItems, and counterAxisAlignItems parameters. It then formats a success or error response.
    async ({ nodeId, primaryAxisAlignItems, counterAxisAlignItems }) => {
      try {
        const result = await sendCommandToFigma("set_axis_align", {
          nodeId,
          primaryAxisAlignItems,
          counterAxisAlignItems
        });
        const typedResult = result as { name: string };
    
        // Create a message about which alignments were set
        const alignMessages = [];
        if (primaryAxisAlignItems !== undefined) alignMessages.push(`primary: ${primaryAxisAlignItems}`);
        if (counterAxisAlignItems !== undefined) alignMessages.push(`counter: ${counterAxisAlignItems}`);
    
        const alignText = alignMessages.length > 0
          ? `axis alignment (${alignMessages.join(', ')})`
          : "axis alignment";
    
        return {
          content: [
            {
              type: "text",
              text: `Set ${alignText} for frame "${typedResult.name}"`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error setting axis alignment: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
        };
      }
    }
  • Zod schema defining the input parameters for the 'set_axis_align' tool: nodeId (required), primaryAxisAlignItems (optional enum), counterAxisAlignItems (optional enum).
    {
      nodeId: z.string().describe("The ID of the frame to modify"),
      primaryAxisAlignItems: z
        .enum(["MIN", "MAX", "CENTER", "SPACE_BETWEEN"])
        .optional()
        .describe("Primary axis alignment (MIN/MAX = left/right in horizontal, top/bottom in vertical). Note: When set to SPACE_BETWEEN, itemSpacing will be ignored as children will be evenly spaced."),
      counterAxisAlignItems: z
        .enum(["MIN", "MAX", "CENTER", "BASELINE"])
        .optional()
        .describe("Counter axis alignment (MIN/MAX = top/bottom in horizontal, left/right in vertical)")
    },
  • MCP tool registration using server.tool() for 'set_axis_align', including description, input schema, and handler function.
    server.tool(
      "set_axis_align",
      "Set primary and counter axis alignment for an auto-layout frame in Figma",
      {
        nodeId: z.string().describe("The ID of the frame to modify"),
        primaryAxisAlignItems: z
          .enum(["MIN", "MAX", "CENTER", "SPACE_BETWEEN"])
          .optional()
          .describe("Primary axis alignment (MIN/MAX = left/right in horizontal, top/bottom in vertical). Note: When set to SPACE_BETWEEN, itemSpacing will be ignored as children will be evenly spaced."),
        counterAxisAlignItems: z
          .enum(["MIN", "MAX", "CENTER", "BASELINE"])
          .optional()
          .describe("Counter axis alignment (MIN/MAX = top/bottom in horizontal, left/right in vertical)")
      },
      async ({ nodeId, primaryAxisAlignItems, counterAxisAlignItems }) => {
        try {
          const result = await sendCommandToFigma("set_axis_align", {
            nodeId,
            primaryAxisAlignItems,
            counterAxisAlignItems
          });
          const typedResult = result as { name: string };
    
          // Create a message about which alignments were set
          const alignMessages = [];
          if (primaryAxisAlignItems !== undefined) alignMessages.push(`primary: ${primaryAxisAlignItems}`);
          if (counterAxisAlignItems !== undefined) alignMessages.push(`counter: ${counterAxisAlignItems}`);
    
          const alignText = alignMessages.length > 0
            ? `axis alignment (${alignMessages.join(', ')})`
            : "axis alignment";
    
          return {
            content: [
              {
                type: "text",
                text: `Set ${alignText} for frame "${typedResult.name}"`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error setting axis alignment: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
          };
        }
      }
    );
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. It states the tool modifies an auto-layout frame, implying a mutation, but does not disclose any behavioral traits such as permissions required, whether changes are reversible, error conditions (e.g., invalid nodeId), or side effects. The description is minimal and lacks critical context for safe invocation.

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, clear sentence that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and target, making it easy to parse. Every part of the description earns its place by specifying the exact alignment properties and context (auto-layout frame in Figma).

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 the complexity (a mutation tool with no annotations and no output schema), the description is incomplete. It lacks information on behavioral aspects like error handling, permissions, or what the tool returns. While the schema covers parameters well, the description does not compensate for the absence of annotations or output schema, leaving gaps in understanding the tool's full context.

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 detailed descriptions for each parameter, including enum values and their meanings (e.g., MIN/MAX mappings). The description does not add any additional parameter semantics beyond what the schema provides. According to the rules, with high schema coverage (>80%), the baseline score is 3, as the schema adequately documents parameters.

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 ('primary and counter axis alignment for an auto-layout frame in Figma'), making the purpose evident. It specifies the resource type (auto-layout frame) and the exact properties being modified. However, it does not explicitly differentiate from sibling tools like 'set_layout_mode' or 'set_item_spacing', which also configure auto-layout frames.

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 does not mention prerequisites (e.g., the node must be an auto-layout frame), exclusions, or comparisons to sibling tools like 'set_layout_mode' or 'set_item_spacing'. Usage is implied only by the tool's name and description, 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.

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/pipethedev/Talk-to-Figma-MCP'

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