Skip to main content
Glama
sakce

Monday.com MCP Server

by sakce

monday-create-item

Create items or sub-items in a Monday.com board. Specify board ID, item title, and optional group ID or parent item ID to organize tasks efficiently. Set column values for detailed task management.

Instructions

Create a new item in a Monday.com Board. Optionally, specify the parent Item ID to create a Sub-item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesMonday.com Board ID that the Item or Sub-item is on.
columnValuesNoDictionary of column values to set {column_id: value}
groupIdNoMonday.com Board's Group ID to create the Item in. If set, parentItemId should not be set.
itemTitleYesName of the Monday.com Item or Sub-item that will be created.
parentItemIdNoMonday.com Item ID to create the Sub-item under. If set, groupId should not be set.

Implementation Reference

  • Core implementation of the monday-create-item tool logic. Creates an item or subitem on a Monday.com board using the MondayClient API, constructs the item URL, and returns formatted text content.
    async def handle_monday_create_item(
        boardId: str,
        itemTitle: str,
        monday_client: MondayClient,
        groupId: Optional[str] = None,
        parentItemId: Optional[str] = None,
        columnValues: Optional[dict] = None,
    ) -> list[types.TextContent]:
        """Create a new item in a Monday.com Board. Optionally, specify the parent Item ID to create a Sub-item."""
        if parentItemId is None and groupId is not None:
            response = monday_client.items.create_item(
                board_id=boardId,
                group_id=groupId,
                item_name=itemTitle,
                column_values=columnValues,
            )
        elif parentItemId is not None and groupId is None:
            response = monday_client.items.create_subitem(
                parent_item_id=parentItemId,
                subitem_name=itemTitle,
                column_values=columnValues,
            )
        else:
            return [
                types.TextContent(
                    type="text",
                    text="You can set either groupId or parentItemId argument, but not both.",
                )
            ]
    
        try:
            data = response["data"]
            id_key = "create_item" if parentItemId is None else "create_subitem"
            item_url = f"{MONDAY_WORKSPACE_URL}/boards/{boardId}/pulses/{data.get(id_key).get('id')}"
            return [
                types.TextContent(
                    type="text",
                    text=f"Created a new Monday.com item. URL: {item_url}",
                )
            ]
        except Exception as e:
            return [
                types.TextContent(
                    type="text",
                    text=f"Error creating Monday.com item: {e}",
                )
            ]
  • Tool registration for 'monday_create_item' (maps to 'monday-create-item') using FastMCP. Thin wrapper around the core handler, defines input parameters and docstring schema.
    @mcp.tool()
    async def monday_create_item(
        boardId: str,
        itemTitle: str,
        groupId: Optional[str] = None,
        parentItemId: Optional[str] = None,
        columnValues: Optional[Dict[str, Any]] = None,
    ) -> str:
        """Create a new item in a Monday.com Board. Optionally, specify the parent Item ID to create a Sub-item.
    
        Args:
            boardId: Monday.com Board ID that the Item or Sub-item is on.
            itemTitle: Name of the Monday.com Item or Sub-item that will be created.
            groupId: Monday.com Board's Group ID to create the Item in. If set, parentItemId should not be set.
            parentItemId: Monday.com Item ID to create the Sub-item under. If set, groupId should not be set.
            columnValues: Dictionary of column values to set {column_id: value}.
        """
        try:
            client = get_monday_client()
            result = await handle_monday_create_item(
                boardId, itemTitle, groupId, parentItemId, columnValues, client
            )
            return result[0].text
        except Exception as e:
            return f"Error creating item: {e}"
  • Constant used in the handler to construct the URL of the created item.
    MONDAY_WORKSPACE_URL = f"https://{MONDAY_WORKSPACE_NAME}.monday.com"
  • Helper function to initialize and retrieve the MondayClient instance using the API key.
    def get_monday_client() -> MondayClient:
        global monday_client
        if monday_client is None:
            monday_client = MondayClient(MONDAY_API_KEY)
        return monday_client
  • Import of the handle_monday_create_item handler function into the server module for use in tool wrappers.
    from mcp_server_monday.item import (
        handle_monday_archive_item,
        handle_monday_create_item,
        handle_monday_create_update_on_item,
        handle_monday_delete_item,
        handle_monday_get_item_by_id,
        handle_monday_get_item_updates,
        handle_monday_list_items_in_groups,
        handle_monday_list_subitems_in_items,
        handle_monday_move_item_to_group,
        handle_monday_update_item,
    )
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. It states the tool creates items but does not disclose behavioral traits such as required permissions, whether creation is idempotent, rate limits, or what happens on failure. This is a significant gap for a mutation tool with no annotation coverage.

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 and adds optional functionality. There is no wasted language, and it is appropriately sized for the tool's complexity.

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 tool's complexity (mutation with 5 parameters, no annotations, no output schema), the description is incomplete. It lacks details on behavioral aspects like error handling, permissions, and return values, which are crucial for an agent to use the tool effectively in context with siblings.

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%, so the schema already documents all parameters thoroughly. The description adds minimal value by mentioning the optional parent Item ID for Sub-items, but does not provide additional semantics beyond what the schema specifies. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Create' and the resource 'new item in a Monday.com Board', with additional specificity about creating Sub-items. It distinguishes from siblings like 'monday-create-board' (creates boards) and 'monday-create-update' (creates updates), making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by mentioning 'Optionally, specify the parent Item ID to create a Sub-item', which hints at when to use it for sub-items versus regular items. However, it lacks explicit guidance on when to use this tool versus alternatives like 'monday-create-board' or 'monday-create-doc', and does not mention prerequisites or exclusions beyond the optional parentItemId.

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