Skip to main content
Glama
sakce

Monday.com MCP Server

by sakce

monday-get-board-columns

Retrieve column details for a specific Monday.com board by providing the board ID. Use this tool to fetch structured column information for efficient board management.

Instructions

Get the Columns of a Monday.com Board.

Input Schema

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

Implementation Reference

  • The core handler function that implements the logic for retrieving board columns from Monday.com using GraphQL query, processes column settings, and returns formatted text content.
    async def handle_monday_get_board_columns(
        boardId: str, monday_client: MondayClient
    ) -> list[types.TextContent]:
        """Get the Columns of a Monday.com Board."""
        query = f"""
            query {{
                boards(ids: {boardId}) {{
                    columns {{
                        id
                        title
                        type
                        settings_str
                    }}
                }}
            }}
        """
        response = monday_client.custom._query(query)
        for board in response.get("data", {}).get("boards", []):
            for column in board["columns"]:
                settings_str = column.pop("settings_str", None)
                if settings_str:
                    if isinstance(settings_str, str):
                        try:
                            settings_obj = json.loads(settings_str)
                            if settings_obj.get("labels"):
                                column["available_labels"] = settings_obj["labels"]
                        except json.JSONDecodeError:
                            pass
    
        return [
            types.TextContent(
                type="text",
                text=f"Got the columns of a Monday.com board:\n{json.dumps(response)}",
            )
        ]
  • Tool registration using FastMCP's @mcp.tool() decorator. This wrapper function initializes the Monday client, calls the core handler, and handles errors, exposing the tool as 'monday-get-board-columns'.
    @mcp.tool()
    async def monday_get_board_columns(boardId: str) -> str:
        """Get the Columns of a Monday.com Board.
    
        Args:
            boardId: Monday.com Board ID that the Item or Sub-item is on.
        """
        try:
            client = get_monday_client()
            result = await handle_monday_get_board_columns(boardId, client)
            return result[0].text
        except Exception as e:
            return f"Error getting board columns: {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 it's a 'Get' operation, implying read-only behavior, but doesn't specify authentication needs, rate limits, error conditions, or what the return format looks like (e.g., JSON structure). For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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, clear sentence with zero wasted words. It's front-loaded with the core purpose ('Get the Columns'), making it easy to scan. Every word earns its place, and there's no redundancy or unnecessary elaboration.

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 doesn't explain what the tool returns (e.g., column types, IDs, settings) or any behavioral traits like error handling. For a tool that likely returns structured data, this omission makes it harder for an agent to use effectively without trial and error.

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 description adds no parameter information beyond what the input schema provides. The schema has 100% description coverage, with the 'boardId' parameter clearly documented. Since the schema does the heavy lifting, the baseline score of 3 is appropriate—the description doesn't add value here, but it doesn't need to compensate for gaps.

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 ('Get') and resource ('Columns of a Monday.com Board'), making the purpose immediately understandable. It distinguishes from siblings like 'monday-get-board-groups' (which gets groups, not columns) and 'monday-list-boards' (which lists boards, not columns). However, it doesn't specify the scope (e.g., all columns vs. specific types), which prevents a perfect score.

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 prerequisites (e.g., needing a board ID), exclusions, or comparisons to siblings like 'monday-get-board-groups' or 'monday-list-items-in-groups'. The agent must infer usage from the tool 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