Skip to main content
Glama

delete-group

Remove a specific group from a Miro board, with options to delete or preserve the items within the group.

Instructions

Delete a specific group from a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesID of the board that contains the group
groupIdYesID of the group that you want to delete
deleteItemsNoIndicates whether the items should be removed. Set to true to delete items in the group, false to keep them

Implementation Reference

  • The asynchronous handler function that implements the logic for the 'delete-group' tool. It validates inputs, calls the Miro API to delete the group, and returns a 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");
        }
    
        await MiroClient.getApi().deleteGroup(boardId, groupId, deleteItems ?? false);
    
        return ServerResponse.text(JSON.stringify({ success: true, message: "Group successfully deleted" }, null, 2));
      } catch (error) {
        process.stderr.write(`Error deleting group: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • The schema definition for the 'delete-group' tool, including name, description, and Zod input schema for parameters boardId, groupId, and optional deleteItems.
    name: "delete-group",
    description: "Delete a specific group from a Miro board",
    args: {
      boardId: z.string().describe("ID of the board that contains the group"),
      groupId: z.string().describe("ID of the group that you want to delete"),
      deleteItems: z.boolean().optional().nullish().describe("Indicates whether the items should be removed. Set to true to delete items in the group, false to keep them")
    },
  • src/index.ts:184-184 (registration)
    The registration of the deleteGroupTool in the ToolBootstrapper chain in the main index file.
    .register(deleteGroupTool)
Behavior2/5

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

No annotations are provided, so the description carries full burden. While 'Delete' implies a destructive mutation, it doesn't disclose critical behavioral traits: whether deletion is permanent or reversible, what permissions are required, how it affects board structure, or error conditions. The description mentions the tool deletes a group but lacks context on consequences beyond what's implied by the verb.

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, clear sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately scannable and efficient. Every word earns its place by conveying essential information without redundancy.

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?

For a destructive mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral risks, permissions, or what happens to items in the group (though deleteItems parameter hints at this). Given the complexity of deletion operations and lack of structured safety hints, more context about consequences and usage would be warranted.

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 three parameters thoroughly. The description adds no additional meaning about parameters beyond what's in the schema (e.g., it doesn't explain format of IDs or default behavior for deleteItems). Baseline 3 is appropriate since the schema does the heavy lifting.

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 ('Delete') and resource ('a specific group from a Miro board'), making the purpose immediately understandable. It distinguishes itself from siblings like 'delete-board' or 'delete-item' by specifying the target is a group. However, it doesn't explicitly differentiate from 'ungroup-items', which might have overlapping functionality.

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. With siblings like 'delete-item', 'delete-board', and 'ungroup-items' available, there's no indication of when group deletion is appropriate versus other deletion operations or whether prerequisites like permissions are needed.

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