Skip to main content
Glama

clone_node

Duplicate Figma design elements by creating copies at specified coordinates. Use this tool to replicate nodes within your Figma workspace.

Instructions

Clone an existing node in Figma

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the node to clone
xNoNew X position for the clone
yNoNew Y position for the clone

Implementation Reference

  • Handler function for the 'clone_node' MCP tool. Registers the tool, defines input schema (nodeId required, x/y optional), and proxies execution to Figma plugin via sendCommandToFigma('clone_node'). Returns success message with new node ID or error.
    // Clone Node Tool
    server.tool(
      "clone_node",
      "Clone an existing node in Figma",
      {
        nodeId: z.string().describe("The ID of the node to clone"),
        x: z.number().optional().describe("New X position for the clone"),
        y: z.number().optional().describe("New Y position for the clone")
      },
      async ({ nodeId, x, y }) => {
        try {
          const result = await sendCommandToFigma('clone_node', { nodeId, x, y });
          const typedResult = result as { name: string, id: string };
          return {
            content: [
              {
                type: "text",
                text: `Cloned node "${typedResult.name}" with new ID: ${typedResult.id}${x !== undefined && y !== undefined ? ` at position (${x}, ${y})` : ''}`
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error cloning node: ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          };
        }
      }
    );
  • Input schema for clone_node tool using Zod: nodeId (string, required), x (number, optional), y (number, optional).
    {
      nodeId: z.string().describe("The ID of the node to clone"),
      x: z.number().optional().describe("New X position for the clone"),
      y: z.number().optional().describe("New Y position for the clone")
    },
  • Registration of 'clone_node' tool on McpServer instance with name, description, schema, and handler.
    // Clone Node Tool
    server.tool(
      "clone_node",
      "Clone an existing node in Figma",
      {
        nodeId: z.string().describe("The ID of the node to clone"),
        x: z.number().optional().describe("New X position for the clone"),
        y: z.number().optional().describe("New Y position for the clone")
      },
      async ({ nodeId, x, y }) => {
        try {
          const result = await sendCommandToFigma('clone_node', { nodeId, x, y });
          const typedResult = result as { name: string, id: string };
          return {
            content: [
              {
                type: "text",
                text: `Cloned node "${typedResult.name}" with new ID: ${typedResult.id}${x !== undefined && y !== undefined ? ` at position (${x}, ${y})` : ''}`
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              {
                type: "text",
                text: `Error cloning node: ${error instanceof Error ? error.message : String(error)}`
              }
            ]
          };
        }
      }
    );
  • TypeScript type definition for clone_node command parameters in CommandParams union.
    clone_node: {
      nodeId: string;
      x?: number;
      y?: number;
    };
  • Inclusion of 'clone_node' in FigmaCommand type union for sendCommandToFigma.
    | "clone_node"
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. 'Clone an existing node' implies a mutation operation but doesn't specify whether this requires edit permissions, what happens to the original node, or if there are rate limits. It lacks details about the cloning behavior (e.g., does it copy styles, children, or overrides?).

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 directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 inadequate. It doesn't explain what the clone operation returns, what happens on failure, or important behavioral aspects like whether the clone inherits all properties. Given the complexity of node operations in Figma, more context is needed.

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 already documents all three parameters (nodeId, x, y) adequately. The description doesn't add any additional meaning beyond what's in the schema, such as explaining coordinate systems or node ID formats, but it doesn't need to given the 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 ('Clone') and target resource ('an existing node in Figma'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'create_frame' or 'create_rectangle' that also create new nodes, leaving some ambiguity about when cloning is preferable to creation.

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 like 'create_frame' or 'create_rectangle', nor does it mention prerequisites such as needing an existing node ID. There's no context about appropriate use cases or limitations.

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