Skip to main content
Glama
sakce

Monday.com MCP Server

by sakce

monday-list-items-in-groups

Retrieve all items in specified groups of a Monday.com board by providing the board ID, group IDs, and limit. Organize and manage board data effectively.

Instructions

List all items in the specified groups of a Monday.com board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesMonday.com Board ID that the Item or Sub-item is on.
cursorNo
groupIdsYes
limitYes

Implementation Reference

  • Core implementation of the tool logic: constructs a GraphQL query to fetch items from specified groups in a board, executes it via monday_client, and returns formatted text content.
    async def handle_monday_list_items_in_groups(
        boardId: str,
        groupIds: list[str],
        limit: int,
        monday_client: MondayClient,
        cursor: Optional[str] = None,
    ) -> list[types.TextContent]:
        """List all items in the specified groups of a Monday.com board"""
    
        if groupIds and not cursor:
            formatted_group_ids = ", ".join([f'"{group_id}"' for group_id in groupIds])
            items_page_params = f"""
                query_params: {{
                    rules: [
                        {{column_id: "group", compare_value: [{formatted_group_ids}], operator: any_of}}
                    ]
                }}
            """
        else:
            items_page_params = f'cursor: "{cursor}"'
    
        items_page_params += f" limit: {limit}"
        query = f"""
        query {{
            boards (ids: {boardId}) {{
                items_page ({items_page_params}) {{
                    cursor
                    items {{
                        id
                        name
                        updates {{
                            id
                            body
                        }}
                        column_values {{
                            id
                            text
                            value
                        }}
                    }}
                }}
            }}
        }}
        """
    
        response = monday_client.custom._query(query)
        return [
            types.TextContent(
                type="text",
                text=f"Items in groups {groupIds} of Monday.com board {boardId}: {json.dumps(response)}",
            )
        ]
  • MCP tool registration using @mcp.tool() decorator. This wrapper function defines the tool interface, fetches the Monday client, calls the core handler, and handles errors.
    @mcp.tool()
    async def monday_list_items_in_groups(
        boardId: str, groupIds: List[str], limit: int, cursor: Optional[str] = None
    ) -> str:
        """List all items in the specified groups of a Monday.com board.
    
        Args:
            boardId: Monday.com Board ID that the Item or Sub-item is on.
            groupIds: List of group IDs to list items from.
            limit: Maximum number of items to return.
            cursor: Pagination cursor for continuing from previous results.
        """
        try:
            client = get_monday_client()
            result = await handle_monday_list_items_in_groups(
                boardId, groupIds, limit, cursor, client
            )
            return result[0].text
        except Exception as e:
            return f"Error listing items in groups: {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 this is a list operation, implying it's read-only and non-destructive, but doesn't mention pagination behavior (despite 'cursor' and 'limit' parameters), rate limits, authentication needs, or error handling. This leaves significant gaps for a tool with multiple parameters and no output schema.

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 without unnecessary words. Every part of the sentence earns its place by specifying the action, scope, and target resource.

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 complexity (4 parameters, 3 required), low schema coverage (25%), and lack of annotations and output schema, the description is incomplete. It doesn't address behavioral aspects like pagination or error handling, nor does it clarify parameter usage, making it inadequate for reliable tool invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is low at 25%, with only 'boardId' documented. The description adds no parameter semantics beyond what's implied by the tool name ('specified groups'), failing to explain 'cursor' (likely for pagination), 'groupIds' (array of group identifiers), or 'limit' (max items to return). This doesn't compensate for the poor 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 ('List all items') and target resource ('in the specified groups of a Monday.com board'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'monday-get-items-by-id' or 'monday-list-subitems-in-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. It doesn't mention sibling tools like 'monday-get-items-by-id' (for specific items) or 'monday-list-subitems-in-items' (for subitems), nor does it specify prerequisites or exclusions, leaving the agent to infer usage from the name alone.

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