Skip to main content
Glama
sakce

Monday.com MCP Server

by sakce

monday-list-boards

Retrieve all boards from Monday.com with customizable pagination, enabling efficient management and access to board information.

Instructions

Get all Boards from Monday.com

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of Monday.com Boards to return.
pageNoPage number for pagination.

Implementation Reference

  • Core handler function that implements the logic to list Monday.com boards: fetches boards using the client, formats a list of board names and IDs, and returns as TextContent.
    async def handle_monday_list_boards(
        monday_client: MondayClient, limit: int, page: int
    ) -> list[types.TextContent]:
        """List all available Monday.com boards"""
        response = monday_client.boards.fetch_boards(limit=limit, page=page)
        boards = response["data"]["boards"]
    
        board_list = "\n".join(
            [f"- {board['name']} (ID: {board['id']})" for board in boards]
        )
    
        return [
            types.TextContent(
                type="text", text=f"Available Monday.com Boards:\n{board_list}"
            )
        ]
  • MCP tool registration using @mcp.tool() decorator for the 'monday_list_boards' tool, which handles input parameters, retrieves the Monday client, calls the core handler, and returns the result as string.
    @mcp.tool()
    async def monday_list_boards(limit: int = 100, page: int = 1) -> str:
        """Get all Boards from Monday.com.
    
        Args:
            limit: Maximum number of Monday.com Boards to return.
            page: Page number for pagination.
        """
        try:
            client = get_monday_client()
            result = await handle_monday_list_boards(client, limit, page)
            return result[0].text
        except Exception as e:
            return f"Error listing boards: {e}"
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. It states 'Get all Boards' but does not mention authentication requirements, rate limits, pagination behavior beyond the schema, or what 'all' entails (e.g., workspace scope). This leaves significant gaps for a read operation with potential complexity.

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 with zero waste, directly stating the tool's purpose without unnecessary details. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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?

Given the lack of annotations and output schema, the description is incomplete. It does not explain return values, error handling, or behavioral nuances like pagination or filtering. For a tool with two parameters and no structured output, more context is needed to guide 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?

The input schema has 100% description coverage, with clear documentation for 'limit' and 'page' parameters. The description adds no additional meaning beyond the schema, such as default values or usage examples. With high schema coverage, the baseline score of 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 'Get' and the resource 'all Boards from Monday.com', making the purpose evident. However, it does not explicitly differentiate from sibling tools like 'monday-get-board-columns' or 'monday-get-docs', which also retrieve data but target different resources, so it lacks sibling differentiation.

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, such as 'monday-list-items-in-groups' or 'monday-get-items-by-id' for more specific queries. It lacks context on prerequisites, exclusions, or comparisons with sibling tools, offering only a basic statement of function.

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

Related 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/sakce/mcp-server-monday'

If you have feedback or need assistance with the MCP directory API, please join our Discord server