Skip to main content
Glama
neozhehan

Figma Edit MCP

Ungroup Node

node_ungroup
Destructive

Dissolve a selected group in Figma, moving its children to the parent level and removing the group container.

Instructions

Dissolve a group, promoting its children to the parent. Removes the group container.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeIdYesThe ID of the group to ungroup
nodeNameYesName of the group to verify against

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
parentIdYesID of the parent node (null if the group had no parent)
ungroupedChildrenYesList of ungrouped child nodes
Behavior3/5

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

The description states 'Removes the group container,' which aligns with the 'destructiveHint: true' annotation. It adds minimal context about child promotion beyond the annotation, but does not contradict. With annotations already covering destructive behavior, the description's contribution is adequate but not rich.

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?

Two concise sentences with no extraneous information. The description is front-loaded with the action ('Dissolve a group') and efficiently conveys the tool's behavior.

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

Completeness5/5

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

For a simple ungroup operation, the description sufficiently covers the action and consequences (children promoted, group removed). An output schema is present (not shown), so return values need not be explained. No gaps remain given the tool's complexity.

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 coverage is 100%, with both parameters described in the schema. The description does not add any additional meaning beyond the schema—it only restates the function. Baseline score of 3 is appropriate.

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 clearly states the tool's purpose: 'Dissolve a group, promoting its children to the parent. Removes the group container.' It uses specific verbs ('dissolve', 'ungroup') and identifies the resource (group), distinguishing it from siblings like 'node_group' and 'node_flatten'.

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. Sibling tools like 'node_group' (grouping) and 'node_flatten' are present but not mentioned, leaving the agent without context on when to choose this over others.

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