Skip to main content
Glama
Sign In
OpenCode Figma MCP

OpenCode Figma MCP

by yhoyoex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_parent

Move a Figma node into a new parent such as a section, frame, or group. Keeps the node's absolute position unless you pass x/y coordinates.

Instructions

Move a node into a new parent node (e.g. a section, frame or group). Preserves the node's absolute position unless x/y are provided

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "nodeId": "<nodeId>",
      "parentId": "<parentId>"
    },
    "name": "set_parent"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoOptional X position relative to the new parent
yNoOptional Y position relative to the new parent
indexNoOptional child index to insert at (default: appended as last child)
nodeIdYesThe ID of the node to move
parentIdYesThe ID of the new parent node (must support children, e.g. a section, frame or group)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds the key behavioral detail that the node's absolute position is preserved unless x/y are provided, which is not fully obvious from the schema. It does not discuss reversibility or side effects on children, but the disclosed positioning behavior is valuable and not contradictory.

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 one useful sentence plus a short behavioral clause, with the core action front-loaded. There is no filler or repetition of the input schema.

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 mutating tool with no annotations and no output schema, the description covers the essential operation and the most important behavioral caveat (absolute position preservation). It could mention failure cases or return behavior, but the parameters are fully documented and the core call is clear.

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 five parameters adequately. The description adds minor semantic nuance by linking x/y to absolute-position preservation, but it does not meaningfully expand beyond the schema's parameter descriptions.

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 states a specific verb ('move'), a resource ('a node'), and the target ('into a new parent node'), and the example parent types make the operation concrete. However, it does not explicitly distinguish itself from the sibling tool 'move_node', so clarity is strong but sibling differentiation is left to inference.

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 explicit guidance on when to use set_parent versus alternatives like move_node or clone_node. It implies a reparenting use case but never states when this tool is preferred or what the alternatives are for positioning-only changes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools