Skip to main content
Glama

group_items

Groups Miro items by ID so they move together, or ungroups a specified group and returns the freed item IDs.

Instructions

Group items (ids) so they move together, or ungroup a group (ungroupId). Returns the group, or the freed item ids.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "group_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNo
ungroupIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare it is a non-read-only, non-destructive, closed-world mutation, so the safety profile is covered. The description usefully adds the behavioral consequence ('so they move together') and names what is returned, but omits reversibility, constraints (same parent/board), and what happens if both parameters are supplied.

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

Conciseness4/5

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

A single compact sentence that front-loads the operation and folds the inverse mode and return value in without waste. Slightly dense with parenthetical parameter names, but nothing is redundant.

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

Completeness3/5

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

The tool is simple with two parameters and no output schema, so little is needed; the return values are mentioned. However, the mutual exclusivity of ids versus ungroupId and the failure behavior (neither parameter supplied, since neither is required) are unaddressed.

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 0% and both parameters are undescribed in the schema, so the description must carry the load. It does identify the role of each parameter (ids for grouping, ungroupId for ungrouping) but adds no detail on ordering, minimum size, or how they interact when both are present.

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?

States a specific verb and resource ('Group items') plus the inverse operation, and names the parameter that triggers each mode. Siblings like arrange_items and reorder_items exist but the description does not explicitly contrast with them, so it stops short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by mapping ids to grouping and ungroupId to ungrouping, which tells the agent which mode it is in. There is no explicit when-to-use versus arrange_items/reorder_items, no statement that the two parameters are mutually exclusive, and no note on prerequisites.

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