Skip to main content
Glama
paragdesai1

Cursor Talk to Figma MCP

by paragdesai1

move_node

Reposition design elements in Figma by specifying new X and Y coordinates for precise layout adjustments.

Instructions

Move a node to a new position in Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the node to move
xYesNew X position
yYesNew Y position

Implementation Reference

  • The execution handler for the move_node MCP tool. It forwards the nodeId, x, y parameters to the Figma plugin via sendCommandToFigma and returns a textual response with the result or error.
    async ({ nodeId, x, y }) => {
      try {
        const result = await sendCommandToFigma("move_node", { nodeId, x, y });
        const typedResult = result as { name: string };
        return {
          content: [
            {
              type: "text",
              text: `Moved node "${typedResult.name}" to position (${x}, ${y})`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error moving node: ${error instanceof Error ? error.message : String(error)
                }`,
            },
          ],
        };
      }
    }
  • Zod input schema for the move_node tool defining required parameters: nodeId (string), x (number), y (number).
    {
      nodeId: z.string().describe("The ID of the node to move"),
      x: z.number().describe("New X position"),
      y: z.number().describe("New Y position"),
    },
  • Registration of the move_node tool on the MCP server using server.tool(), including name, description, input schema, and handler function.
    server.tool(
      "move_node",
      "Move a node to a new position in Figma",
      {
        nodeId: z.string().describe("The ID of the node to move"),
        x: z.number().describe("New X position"),
        y: z.number().describe("New Y position"),
      },
      async ({ nodeId, x, y }) => {
        try {
          const result = await sendCommandToFigma("move_node", { nodeId, x, y });
          const typedResult = result as { name: string };
          return {
            content: [
              {
                type: "text",
                text: `Moved node "${typedResult.name}" to position (${x}, ${y})`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error moving node: ${error instanceof Error ? error.message : String(error)
                  }`,
              },
            ],
          };
        }
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('move a node') but doesn't cover critical traits: whether this is a destructive mutation (likely yes, but unconfirmed), permission requirements, rate limits, error conditions (e.g., invalid coordinates), or what happens on success (e.g., no return value mentioned). 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 action ('Move a node') and specifies the context ('in Figma'). There is no wasted verbiage or redundancy, making it easy for an agent to parse quickly and accurately.

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 (a mutation operation with 3 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral risks (e.g., destructive effects), success/failure outcomes, or integration with sibling tools (e.g., how to obtain nodeId from 'get_node_info'). For a mutation tool in this context, more detail is needed to guide safe and 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?

The input schema has 100% description coverage, with clear parameter definitions (nodeId, x, y). The description adds no additional semantic context beyond implying positional movement, which the schema already covers. According to rules, with high schema coverage (>80%), the baseline is 3 even without param info in the description, which applies here.

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 verb ('move') and resource ('a node'), specifying the action and target. It distinguishes from siblings like 'resize_node' or 'delete_node' by focusing on positional change rather than size alteration or removal. However, it doesn't explicitly differentiate from tools like 'set_axis_align' that might also affect positioning, keeping it from a perfect score.

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 nodeId from other tools), exclusions (e.g., not for moving groups of nodes), or comparisons to siblings like 'resize_node' for size changes or 'set_axis_align' for alignment adjustments. This lack of context leaves the agent to infer usage 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/paragdesai1/parag-Figma-MCP'

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