Skip to main content
Glama

get-all-groups

Retrieve all groups from a Miro board to manage and organize visual elements. Specify board ID, limit results, and use pagination for large boards.

Instructions

Retrieve all groups on a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesID of the board whose groups you want to retrieve
limitNoMaximum number of groups to return (default: 50)
cursorNoCursor for pagination

Implementation Reference

  • The asynchronous handler function that implements the tool logic: validates boardId, prepares options for pagination, fetches groups using MiroClient API, stringifies and returns the result, or handles errors.
    fn: async ({ boardId, limit, cursor }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        const options: any = {};
        if (limit) options.limit = limit;
        if (cursor) options.cursor = cursor;
    
        const result = await MiroClient.getApi().getAllGroups(boardId, options);
    
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        process.stderr.write(`Error retrieving groups: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • Tool schema defining the name, description, and Zod-validated input parameters (boardId required, limit and cursor optional).
    name: "get-all-groups",
    description: "Retrieve all groups on a Miro board",
    args: {
      boardId: z.string().describe("ID of the board whose groups you want to retrieve"),
      limit: z.number().optional().nullish().describe("Maximum number of groups to return (default: 50)"),
      cursor: z.string().optional().nullish().describe("Cursor for pagination")
    },
  • src/index.ts:179-179 (registration)
    Registers the getAllGroupsTool with the MCP ToolBootstrapper in the main index file.
    .register(getAllGroupsTool)
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic operation. It doesn't disclose whether this is a read-only operation (implied by 'retrieve'), potential rate limits, authentication requirements, pagination behavior (though schema hints at it), or what happens when no groups exist. For a tool with 3 parameters and no annotations, this is insufficient.

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, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for a straightforward retrieval tool and front-loads the core purpose.

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?

For a retrieval tool with good schema coverage but no annotations or output schema, the description is minimally adequate. It covers the basic purpose but lacks important context about behavioral traits, differentiation from siblings, and output expectations. The schema handles parameters well, but the description doesn't compensate for missing annotation coverage.

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%, providing clear documentation for all parameters (boardId, limit, cursor). The description doesn't add any meaningful parameter semantics beyond what's already in the schema, so it meets the baseline for high schema coverage without adding value.

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 ('Retrieve all groups') and resource ('on a Miro board'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get-group' (singular) or 'get-group-items', which could cause confusion about scope.

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 about when to use this tool versus alternatives like 'get-group' (for a specific group) or 'get-group-items' (for items within groups). The description simply states what it does without context about appropriate use cases.

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