Skip to main content
Glama
the-real-talk

the-real-talk

group_nodes

Groups selected Figma nodes into one group, with optional name, parent, and insertion index to organize design layers.

Instructions

Group nodes.

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": {
      "nodeIds": "<nodeIds>"
    },
    "name": "group_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
indexNo
nodeIdsYes
parentIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full behavioral burden and delivers nothing. It does not disclose that this is a mutating operation, whether grouping is reversible, how child stacking order or parent relationships change, or whether nodeIds must share a parent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is short but that is under-specification rather than conciseness; it contains no information beyond the title. There is no structure, no front-loaded scope, and nothing to guide invocation.

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

Completeness1/5

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

For a four-parameter mutation tool with no annotations, no output schema, and zero schema description coverage, the definition is completely inadequate. Anything an agent needs in order to call it correctly — required co-location of nodes, effect on existing parents, return value — is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Four parameters with 0% schema description coverage, and the description adds no meaning to any of them. The roles of name, index, parentId, and the 200-item nodeIds cap, and whether index or parentId is required or mutually exclusive, are left entirely unexplained.

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

Purpose2/5

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

"Group nodes" only restates the tool name in slightly different words. It does not say what grouping means here (creating a group node parent, reparenting children, wrapper semantics) or how it differs from siblings like flatten_nodes or combine_as_variants, so an agent must infer the operation entirely.

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

Usage Guidelines1/5

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

There is no when-to-use or when-not-to-use guidance, no prerequisite about node types or pages, and no mention of alternatives such as flatten_nodes or boolean_operation. An agent gets no basis for choosing this tool over its siblings.

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