Skip to main content
Glama
sakce

Monday.com MCP Server

by sakce

monday-update-item

Update column values of a specific item or sub-item on a Monday.com board by providing the board ID, item ID, and column values to modify.

Instructions

Update a Monday.com item's or sub-item's column values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boardIdYesMonday.com Board ID that the Item or Sub-item is on.
columnValuesYesDictionary of column values to update the Monday.com Item or Sub-item with. ({column_id: value})
itemIdYesMonday.com Item or Sub-item ID to update the columns of.

Implementation Reference

  • Core handler function executing the tool logic by calling Monday.com API to update item column values.
    async def handle_monday_update_item(
        boardId: str,
        itemId: str,
        columnValues: dict[str],
        monday_client: MondayClient,
    ):
        response = monday_client.items.change_multiple_column_values(
            board_id=boardId, item_id=itemId, column_values=columnValues
        )
        return [
            types.TextContent(
                type="text", text=f"Updated Monday.com item. {json.dumps(response)}"
            )
        ]
  • Registers the 'monday_update_item' tool with FastMCP (@mcp.tool()), defines input schema via parameters, and delegates to the handler.
    @mcp.tool()
    async def monday_update_item(
        boardId: str, itemId: str, columnValues: Dict[str, Any]
    ) -> str:
        """Update a Monday.com item's or sub-item's column values.
    
        Args:
            boardId: Monday.com Board ID that the Item or Sub-item is on.
            itemId: Monday.com Item or Sub-item ID to update the columns of.
            columnValues: Dictionary of column values to update the Monday.com Item or Sub-item with. ({column_id: value}).
        """
        try:
            client = get_monday_client()
            result = await handle_monday_update_item(boardId, itemId, columnValues, client)
            return result[0].text
        except Exception as e:
            return f"Error updating item: {e}"
  • Input schema defined by function parameters and docstring describing boardId (str), itemId (str), columnValues (Dict[str, Any]). Output is str.
    async def monday_update_item(
        boardId: str, itemId: str, columnValues: Dict[str, Any]
    ) -> str:
        """Update a Monday.com item's or sub-item's column values.
    
        Args:
            boardId: Monday.com Board ID that the Item or Sub-item is on.
            itemId: Monday.com Item or Sub-item ID to update the columns of.
            columnValues: Dictionary of column values to update the Monday.com Item or Sub-item with. ({column_id: value}).
        """
        try:
            client = get_monday_client()
            result = await handle_monday_update_item(boardId, itemId, columnValues, client)
            return result[0].text
        except Exception as e:
            return f"Error updating item: {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 the tool updates column values, implying a mutation, but doesn't describe permissions required, rate limits, side effects (e.g., if updates are reversible), or error handling. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 purpose without unnecessary words. It's front-loaded with the core action ('Update'), making it easy to parse. Every part of the sentence earns its place by specifying the resource and scope.

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 of a mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on behavioral traits (e.g., permissions, side effects), usage context, and return values. While the schema covers parameters well, the overall context for safe and effective use is insufficient.

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 schema description coverage is 100%, so the schema already documents all three parameters (boardId, itemId, columnValues) with clear descriptions. The description adds no additional meaning beyond what's in the schema, such as examples or constraints. Baseline 3 is appropriate when the schema does the heavy lifting, but the description doesn't compensate or enhance understanding.

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 ('Update') and resource ('Monday.com item's or sub-item's column values'), making the purpose immediately understandable. It distinguishes the tool from siblings like 'monday-create-item' or 'monday-delete-item' by focusing on updates rather than creation or deletion. However, it doesn't explicitly differentiate from other update-related tools like 'monday-create-update', which might handle updates differently.

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 board and item IDs), exclusions (e.g., not for creating items), or compare to siblings like 'monday-create-update' for updates. This leaves the agent without context for tool selection in a server with many related tools.

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