Skip to main content
Glama

get-items-on-board

Retrieve all items from a specific Miro board using its unique identifier, with options for pagination and limiting results.

Instructions

Retrieve all items on a specific Miro board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesUnique identifier (ID) of the board whose items you want to retrieve
limitNoMaximum number of items to return (default: 50)
offsetNoOffset for pagination (default: 0)

Implementation Reference

  • The main handler function for the 'get-items-on-board' tool. It fetches items from a Miro board using the MiroClient API, handles pagination with limit (offset not used), and returns JSON data or error.
    fn: async ({ boardId, limit = 50, offset = 0 }) => {
      try {
        if (!boardId) {
          return ServerResponse.error("Board ID is required");
        }
    
        const itemsData = await MiroClient.getApi().getItems(boardId, {
          limit: limit.toString(),
        });
    
        return ServerResponse.text(JSON.stringify(itemsData, null, 2));
      } catch (error) {
        return ServerResponse.error(error);
      }
    }
  • Zod schema defining the input parameters for the tool: boardId (required string), limit and offset (optional numbers).
    args: {
      boardId: z.string().describe("Unique identifier (ID) of the board whose items you want to retrieve"),
      limit: z.number().optional().nullish().describe("Maximum number of items to return (default: 50)"),
      offset: z.number().optional().nullish().describe("Offset for pagination (default: 0)")
    },
  • src/index.ts:117-117 (registration)
    Registers the get-items-on-board tool with the ToolBootstrapper in the main server index file.
    .register(getItemsOnBoardTool)
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. It states 'Retrieve all items' but doesn't disclose behavioral traits like pagination behavior (implied by limit/offset parameters), rate limits, authentication needs, or what 'items' encompasses (e.g., types, formats). This leaves significant gaps for a read operation with pagination.

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 ('Retrieve all items on a specific Miro board'). There is zero wasted text, making it highly concise and well-structured for quick comprehension.

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 tool with 3 parameters, no annotations, and no output schema, the description is inadequate. It lacks details on return values (what 'items' include), pagination behavior, error conditions, or usage context. The agent must rely heavily on schema and inference, leaving gaps in operational understanding.

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%, with clear parameter documentation in the schema (boardId, limit, offset). The description adds no additional parameter semantics beyond implying 'all items' relates to boardId. Baseline 3 is appropriate as 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 verb ('Retrieve') and resource ('all items on a specific Miro board'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get-specific-item' or 'get-group-items', which also retrieve items but with different scopes or filters.

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 'get-specific-item' (for single items) and 'get-group-items' (for items in groups), the agent must infer usage from the name alone, lacking explicit when/when-not instructions or named alternatives.

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