Skip to main content
Glama
neozhehan

Figma Edit MCP

by neozhehan
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Clone Node

node_clone

Duplicates an existing Figma node, optionally repositioning it at new x/y coordinates and returns a new node id.

Instructions

Duplicate an existing node, optionally at a new x/y. Produces a new node id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoNew X position for the clone
yNoNew Y position for the clone
nodeIdYesThe ID of the node to clone
nodeNameYesThe node's current exact name, passed back verbatim from `node_info`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoID of the new cloned node
nameNoName of the cloned node
errorNo
parentIdNoID of the parent the clone was placed into — confirm containment without a follow-up read

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv2.3.3
    • changedInput schema / properties / nodeName / description
      Previous value: -"Name of the node to modify"New value: +"The node's current exact name, passed back verbatim from `node_info`."
    • addedOutput schema / properties / error
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "code": {
+      "description": "Stable machine-readable failure code (see the error playbook)",
+      "type": "string"
+    },
+    "details": {
+      "description": "Optional structured context (e.g. partialMutation, before-values)"
+    },
+    "message": {
+      "description": "Human/agent-readable message embedding its own recovery",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / parentId
      Added value: +{
+  "description": "ID of the parent the clone was placed into — confirm containment without a follow-up read",
+  "type": "string"
+}
    • removedOutput schema / required
      Removed value: -[
-  "id",
-  "name"
-]
  2. Changed1 schema field changedv2.3.2
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +{}
  3. Changed1 schema field changedv2.3.0
    • addedInput schema / additionalProperties
      Added value: +false
  4. Addedv2.0.0

TDQS

A4.2/5.0
Behavior4/5

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

The description discloses the key behavioral trait: it duplicates a node and produces a new id, with optional repositioning. It does not contradict the openWorldHint annotation and adds context about the result. However, it does not elaborate on side effects or preconditions, but the core behavior is transparent.

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 two concise sentences, front-loads the action, and contains no extraneous information. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a relatively simple clone operation, the description covers the essential behavior. The presence of an output schema and full parameter schema reduces the burden. It lacks explicit prerequisites, but the schema's mention of node_info hints at the workflow, making it sufficiently complete.

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 covers all 4 parameters with descriptions, including the notable detail that nodeName must be passed back verbatim from node_info. The description adds no additional parameter semantics beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb 'Duplicate' and identifies the resource 'existing node', clearly distinguishing it from sibling tools like node_rename or node_delete. It also states the outcome (produces a new node id), making the purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly implies when to use this tool—when an existing node needs to be duplicated—and differentiates from creation tools by specifying 'existing node'. However, it does not explicitly exclude alternatives or mention when not to use it, but the context is clear enough.

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/neozhehan/figma-edit-mcp'

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