Skip to main content
Glama

set_workspace_groups

Create, update, or delete labeled group boxes on the ComfyUI canvas. Fit boxes around selected nodes, adjust titles, colors, or padding, and remove groups without affecting nodes.

Instructions

Create, edit and delete the group boxes on the canvas open in the browser.

A group is a labelled rectangle drawn behind the nodes that fall inside it. It holds no membership of its own - which nodes are "in" it is decided by where the box is - so creating one around a list of nodes means fitting the box to them, and that is what this does.

Deleting a group takes only the box: the nodes it framed stay exactly where they are. Get the current groups, with their ids and members, from get_workspace_graph.

Args: create: [{"title": ..., "nodes": ["3", "8"]}] - a box fitted around those nodes. "color" takes a palette name ("green", "blue", "pale_blue", ...) or #rrggbb; "padding" is the gap to the nodes, 10 by default. A group with no nodes needs an explicit "bounding": [x, y, width, height] instead. update: [{"group": <id or title>, ...}] with any of "title", "color", "nodes" (refit around these) or "fit": true (refit around whatever it currently holds, after the nodes inside it have moved). remove: groups to delete, by id or title. scope: "root" for the whole workflow, "active" for the subgraph on screen. client_id: which tab to edit; defaults to the most recently focused one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoroot
createNo
removeNo
updateNo
client_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: groups hold no membership, deleting only removes the box, nodes stay in place, create refits the box to nodes with padding, update can refit the box, and empty groups need an explicit bounding box. This exceeds annotations by providing concrete side-effect information.

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 well-structured with a short lead sentence followed by detailed yet efficient explanations. It uses an Args block for parameter details. Every sentence adds value—there is no fluff. The length is justified by the tool's complexity.

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?

Given zero annotations and zero schema description coverage, the description thoroughly covers all necessary context: what the tool does, how each operation variant works, parameter formats, defaults, and pointers to related tools. The presence of an output schema reduces the need to describe return values, so the description is complete for an agent to use.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden, and it succeeds. It explains each parameter in detail with examples ('create: [{"title": ..., "nodes": ["3", "8"]}]'), defaults ('padding 10', 'scope: root', 'client_id defaulting to most recently focused'), and clarification on behavior ('refit around these', 'refit around whatever it currently holds'). This goes well beyond the minimal schema.

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 opens with 'Create, edit and delete the group boxes on the canvas open in the browser.' This uses a specific verb set and clearly identifies the resource (canvas groups), distinguishing it from sibling tools like set_workspace_selection or set_workspace_layout. The sentence directly conveys the tool's purpose and scope.

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 implicitly guides usage by defining when to use it ('creating one around a list of nodes') and mentioning related tools ('Get the current groups, with their ids and members, from get_workspace_graph'). It does not explicitly state when not to use it or list alternative tools, but the contextual guidance is sufficient.

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/pytraveler/local-comfyui-mcp'

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