Skip to main content
Glama

ungroup-items

Break apart grouped items on a Miro board to edit or reposition individual elements separately.

Instructions

Ungroup a specific group on a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesID of the board that contains the group
groupIdYesID of the group that you want to ungroup
deleteItemsNoIndicates whether the items should be removed. By default, false.

Implementation Reference

  • The handler function that executes the tool logic: validates boardId and groupId, optionally sets deleteItems, calls MiroClient.getApi().unGroup(), and returns success or error response.
    fn: async ({ boardId, groupId, deleteItems }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        if (!groupId) {
          return ServerResponse.error("Group ID is required");
        }
    
        const options: any = {};
        if (deleteItems !== undefined) options.deleteItems = deleteItems;
    
        await MiroClient.getApi().unGroup(boardId, groupId, options);
    
        return ServerResponse.text(JSON.stringify({ success: true, message: "Group successfully ungrouped" }, null, 2));
      } catch (error) {
        process.stderr.write(`Error ungrouping items: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • Input schema defined using Zod for the tool parameters: boardId (string, required), groupId (string, required), deleteItems (boolean, optional).
      boardId: z.string().describe("ID of the board that contains the group"),
      groupId: z.string().describe("ID of the group that you want to ungroup"),
      deleteItems: z.boolean().optional().nullish().describe("Indicates whether the items should be removed. By default, false.")
    },
  • src/index.ts:183-183 (registration)
    Registers the ungroupItemsTool with the ToolBootstrapper instance.
    .register(ungroupItemsTool)
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Ungroup') but doesn't explain what 'ungroup' entails (e.g., whether it disassembles a group into individual items, affects item positions, or requires specific permissions). It also omits details like side effects, error conditions, or response format, which are critical for a mutation tool without structured safety hints.

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 a single, direct sentence that efficiently conveys the core action without unnecessary words. It is front-loaded with the key verb ('Ungroup') and target, making it easy to parse. There is no wasted language, and it fits the tool's straightforward purpose well.

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

Completeness2/5

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

Given the tool's complexity (a mutation operation with 3 parameters), lack of annotations, and no output schema, the description is insufficient. It doesn't cover behavioral aspects like what 'ungroup' does to items, the implications of the 'deleteItems' parameter, or what the tool returns. For a mutation tool without structured safety or output information, more context is needed to guide the agent effectively.

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 parameters (boardId, groupId, deleteItems) with clear descriptions. The description adds no additional meaning beyond what the schema provides, such as clarifying the 'ungroup' operation's effect on parameters. This meets the baseline score of 3 for high schema coverage without extra value from the description.

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 clearly states the action ('Ungroup') and the target ('a specific group on a Miro board'), making the purpose evident. However, it doesn't explicitly differentiate from sibling tools like 'delete-group' or 'update-group', which handle group removal or modification differently, leaving some ambiguity about when to choose this tool over those alternatives.

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. It doesn't mention prerequisites (e.g., needing an existing group), exclusions (e.g., not for deleting groups entirely), or compare it to sibling tools like 'delete-group' (which removes a group) or 'update-group' (which modifies group properties), leaving the agent to infer usage context.

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/k-jarzyna/mcp-miro'

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