Skip to main content
Glama
sakce

Monday.com MCP Server

by sakce

monday-create-board-group

Create a new group within a Monday.com board by specifying the board ID and group name, enabling structured organization of tasks and items.

Instructions

Create a new group in a Monday.com board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesMonday.com Board ID that the group will be created in.
groupNameYesName of the group to create.

Implementation Reference

  • The handler function that executes the core logic for creating a new board group using the Monday.com API.
    async def handle_monday_create_new_board_group(
        monday_client: MondayClient, board_id: str, group_name: str
    ) -> list[types.TextContent]:
        """
        Create a new group in a Monday.com board.
    
        Args:
            monday_client (MondayClient): The Monday.com client.
            board_id (str): The ID of the board.
            group_name (str): The name of the group.
        """
        group = monday_client.groups.create_group(board_id=board_id, group_name=group_name)
        return [
            types.TextContent(
                type="text",
                text=f"Created new group {group_name} in board {board_id}. ID of the new group: {group['data']['create_group']['id']}",
            )
        ]
  • Registers the 'monday_create_board_group' tool (matching 'monday-create-board-group') with FastMCP, providing input schema via args/docstring and delegating to the handler.
    @mcp.tool()
    async def monday_create_board_group(boardId: str, groupName: str) -> str:
        """Create a new group in a Monday.com board.
    
        Args:
            boardId: Monday.com Board ID that the group will be created in.
            groupName: Name of the group to create.
        """
        try:
            client = get_monday_client()
            result = await handle_monday_create_new_board_group(boardId, groupName, client)
            return result[0].text
        except Exception as e:
            return f"Error creating board group: {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 'creates' a new group, implying a write/mutation operation, but doesn't cover permissions required, rate limits, error conditions (e.g., duplicate group names), or what happens on success (e.g., returns a group ID). For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 directly states the tool's function without unnecessary words. It's front-loaded with the core action ('Create a new group') and context ('in a Monday.com board'), making it easy to parse quickly. Every part of the sentence earns its place by conveying essential information.

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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., a group object or ID), error handling, or side effects. While the schema covers parameters well, the lack of behavioral and output information makes it inadequate for an agent to use this tool confidently without additional context.

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 both parameters ('boardId' and 'groupName') clearly documented in the schema. The description doesn't add any parameter-specific details beyond what's in the schema (e.g., format constraints, examples, or relationships between parameters). With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 ('Create a new group') and target resource ('in a Monday.com board'), making the purpose immediately understandable. It distinguishes from siblings like 'monday-create-board' (creates boards) and 'monday-move-item-to-group' (moves items to existing groups). However, it doesn't specify what a 'group' is in Monday.com context, which could help differentiate further from other board-related tools.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention prerequisites (e.g., needing an existing board), when not to use it (e.g., if groups already exist), or alternatives like 'monday-get-board-groups' for checking existing groups first. The description is purely functional without contextual advice.

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