Skip to main content
Glama

set_padding

Adjust padding values for auto-layout frames in Figma designs to control spacing around content within frames.

Instructions

Set padding values for an auto-layout frame in Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the frame to modify
paddingTopNoTop padding value
paddingRightNoRight padding value
paddingBottomNoBottom padding value
paddingLeftNoLeft padding value

Implementation Reference

  • MCP server.tool registration for the 'set_padding' tool. Includes input schema validation with Zod and the complete handler function that proxies the command to the Figma plugin.
    server.tool(
      "set_padding",
      "Set padding values for an auto-layout frame in Figma",
      {
        nodeId: z.string().describe("The ID of the frame to modify"),
        paddingTop: z.number().optional().describe("Top padding value"),
        paddingRight: z.number().optional().describe("Right padding value"),
        paddingBottom: z.number().optional().describe("Bottom padding value"),
        paddingLeft: z.number().optional().describe("Left padding value"),
      },
      async ({ nodeId, paddingTop, paddingRight, paddingBottom, paddingLeft }) => {
        try {
          const result = await sendCommandToFigma("set_padding", {
            nodeId,
            paddingTop,
            paddingRight,
            paddingBottom,
            paddingLeft,
          });
          const typedResult = result as { name: string };
    
          // Create a message about which padding values were set
          const paddingMessages = [];
          if (paddingTop !== undefined) paddingMessages.push(`top: ${paddingTop}`);
          if (paddingRight !== undefined) paddingMessages.push(`right: ${paddingRight}`);
          if (paddingBottom !== undefined) paddingMessages.push(`bottom: ${paddingBottom}`);
          if (paddingLeft !== undefined) paddingMessages.push(`left: ${paddingLeft}`);
    
          const paddingText = paddingMessages.length > 0
            ? `padding (${paddingMessages.join(', ')})`
            : "padding";
    
          return {
            content: [
              {
                type: "text",
                text: `Set ${paddingText} for frame "${typedResult.name}"`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error setting padding: ${error instanceof Error ? error.message : String(error)}`,
              },
            ],
          };
        }
      }
    );
  • Zod input schema for set_padding tool defining parameters: nodeId (string), and optional paddingTop, paddingRight, paddingBottom, paddingLeft (numbers).
    {
      nodeId: z.string().describe("The ID of the frame to modify"),
      paddingTop: z.number().optional().describe("Top padding value"),
      paddingRight: z.number().optional().describe("Right padding value"),
      paddingBottom: z.number().optional().describe("Bottom padding value"),
      paddingLeft: z.number().optional().describe("Left padding value"),
    },
  • Handler implementation for set_padding tool. Sends the padding parameters to Figma plugin using sendCommandToFigma and constructs a descriptive success message based on which paddings were set.
    async ({ nodeId, paddingTop, paddingRight, paddingBottom, paddingLeft }) => {
      try {
        const result = await sendCommandToFigma("set_padding", {
          nodeId,
          paddingTop,
          paddingRight,
          paddingBottom,
          paddingLeft,
        });
        const typedResult = result as { name: string };
    
        // Create a message about which padding values were set
        const paddingMessages = [];
        if (paddingTop !== undefined) paddingMessages.push(`top: ${paddingTop}`);
        if (paddingRight !== undefined) paddingMessages.push(`right: ${paddingRight}`);
        if (paddingBottom !== undefined) paddingMessages.push(`bottom: ${paddingBottom}`);
        if (paddingLeft !== undefined) paddingMessages.push(`left: ${paddingLeft}`);
    
        const paddingText = paddingMessages.length > 0
          ? `padding (${paddingMessages.join(', ')})`
          : "padding";
    
        return {
          content: [
            {
              type: "text",
              text: `Set ${paddingText} for frame "${typedResult.name}"`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error setting padding: ${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 full burden. It implies a mutation ('Set') but doesn't disclose behavioral traits such as required permissions, whether changes are reversible, error handling (e.g., if nodeId is invalid), or side effects. This is inadequate for a mutation tool with zero annotation coverage.

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 front-loads the core purpose without unnecessary words. Every part earns its place by specifying the action and target clearly.

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 tool's complexity as a mutation with no annotations and no output schema, the description is incomplete. It lacks details on behavioral context (e.g., success/failure responses, constraints), making it insufficient for safe and effective use by an AI agent.

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 parameters in the schema. The description adds no additional meaning beyond what the schema provides, such as units for padding values or default behaviors. Baseline 3 is appropriate as 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 padding values') and target resource ('auto-layout frame in Figma'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'set_item_spacing' or 'set_layout_mode' that also modify layout properties, missing explicit distinction.

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 doesn't mention prerequisites (e.g., the frame must exist and be in auto-layout mode), exclusions, or comparisons with similar tools like 'set_item_spacing' for spacing between items versus padding within a frame.

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