Skip to main content
Glama

get-group-items

Retrieve all items from a specific group on a Miro board to access organized content and manage board elements efficiently.

Instructions

Retrieve all items in a specific group on a Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesID of the board that contains the group
groupIdYesID of the group whose items you want to retrieve
limitNoMaximum number of items to return (default: 50)
cursorNoCursor for pagination

Implementation Reference

  • The asynchronous handler function that implements the tool logic: validates inputs, calls MiroClient.getApi().getItemsByGroupId with optional pagination, and returns the JSON result or error response.
    fn: async ({ boardId, groupId, limit, cursor }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        if (!groupId) {
          return ServerResponse.error("Group ID is required");
        }
    
        const options: any = {};
        if (limit) options.limit = limit;
        if (cursor) options.cursor = cursor;
    
        const result = await MiroClient.getApi().getItemsByGroupId(boardId, groupId, options);
    
        return ServerResponse.text(JSON.stringify(result, null, 2));
      } catch (error) {
        process.stderr.write(`Error retrieving group items: ${error}\n`);
        return ServerResponse.error(error);
      }
    }
  • Zod-based input schema defining required boardId and groupId, optional limit and cursor for pagination.
    args: {
      boardId: z.string().describe("ID of the board that contains the group"),
      groupId: z.string().describe("ID of the group whose items you want to retrieve"),
      limit: z.number().optional().nullish().describe("Maximum number of items to return (default: 50)"),
      cursor: z.string().optional().nullish().describe("Cursor for pagination")
    },
  • src/index.ts:181-181 (registration)
    Registers the getGroupItemsTool with the ToolBootstrapper instance in the main index file.
    .register(getGroupItemsTool)
  • src/index.ts:80-80 (registration)
    Imports the getGroupItemsTool from its definition file for registration.
    import getGroupItemsTool from './tools/getGroupItems.js';
  • Complete ToolSchema definition including name, description, input args schema, and handler function.
    const getGroupItemsTool: ToolSchema = {
      name: "get-group-items",
      description: "Retrieve all items in a specific group on a Miro board",
      args: {
        boardId: z.string().describe("ID of the board that contains the group"),
        groupId: z.string().describe("ID of the group whose items you want to retrieve"),
        limit: z.number().optional().nullish().describe("Maximum number of items to return (default: 50)"),
        cursor: z.string().optional().nullish().describe("Cursor for pagination")
      },
      fn: async ({ boardId, groupId, limit, cursor }) => {
        try {
          if (!boardId) {
            return ServerResponse.error("Board ID is required");
          }
    
          if (!groupId) {
            return ServerResponse.error("Group ID is required");
          }
    
          const options: any = {};
          if (limit) options.limit = limit;
          if (cursor) options.cursor = cursor;
    
          const result = await MiroClient.getApi().getItemsByGroupId(boardId, groupId, options);
    
          return ServerResponse.text(JSON.stringify(result, null, 2));
        } catch (error) {
          process.stderr.write(`Error retrieving group items: ${error}\n`);
          return ServerResponse.error(error);
        }
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a retrieval operation, implying it's read-only, but doesn't mention pagination behavior (implied by 'cursor' parameter), rate limits, authentication needs, or what 'items' encompass. This leaves significant gaps for a tool with 4 parameters.

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 front-loads the core purpose. There's zero wasted language, and it immediately communicates what the tool does without unnecessary elaboration.

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 4 parameters and 100% schema coverage but no annotations or output schema, the description is minimally adequate. It states the purpose clearly but lacks behavioral context (pagination, item types) and usage guidelines compared to siblings, leaving room for improvement.

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 thoroughly. The description adds no additional parameter information beyond what's in the schema (e.g., doesn't explain item types or group relationships). Baseline 3 is appropriate when 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 verb ('Retrieve') and resource ('all items in a specific group on a Miro board'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get-all-groups' or 'get-items-on-board', which would require 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 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 like 'get-all-groups' (which lists groups) or 'get-items-on-board' (which retrieves items without group filtering). There's no mention of prerequisites, exclusions, or comparative 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