Skip to main content
Glama

create-group

Organize Miro board items by creating groups to structure content and improve visual organization.

Instructions

Create a new group on a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesID of the board where the group will be created
dataYesGroup data with item IDs to include in the group

Implementation Reference

  • The handler function that implements the create-group tool logic. It validates inputs, calls MiroClient.getApi().createGroup, and handles errors.
    fn: async ({ boardId, data }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        if (!data || !data.items || data.items.length === 0) {
          return ServerResponse.error("At least one item ID is required in the 'items' array");
        }
    
        const result = await MiroClient.getApi().createGroup(boardId, { data });
    
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        process.stderr.write(`Error creating group: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • Zod schema defining the input parameters: boardId (string) and data (object with items array).
    args: {
      boardId: z.string().describe("ID of the board where the group will be created"),
      data: z.object({
        items: z.array(z.string()).describe("List of item IDs to include in the group")
      }).describe("Group data with item IDs to include in the group")
    },
  • src/index.ts:178-178 (registration)
    Registers the createGroupTool with the ToolBootstrapper instance.
    .register(createGroupTool)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'create' implies a write operation, it doesn't specify permissions required, whether the group is editable after creation, or what happens if item IDs are invalid. This leaves significant behavioral gaps for a mutation tool.

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 no wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse.

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 mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on permissions, error handling, return values, or how the group integrates with other board elements, leaving the agent with incomplete context for safe and effective use.

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 fully documents both parameters (boardId and data with items). The description adds no additional parameter semantics beyond what's in the schema, such as format examples or constraints, meeting the baseline for high schema coverage.

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 ('create') and resource ('new group on a Miro board'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'create-frame' or 'create-shape-item' that also create board elements, missing full sibling distinction.

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?

No guidance is provided on when to use this tool versus alternatives like 'create-items-in-bulk' or 'ungroup-items', nor does it mention prerequisites such as board access or permissions. The description only states what it does, not when or why to use it.

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