Skip to main content
Glama
sakce

Monday.com MCP Server

by sakce

monday-create-update

Add comments to Monday.com Items or Sub-items by providing the item ID and update text, enabling clear communication and task tracking in boards.

Instructions

Create an update (comment) on a Monday.com Item or Sub-item.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdYes
updateTextYesContent to update the Item or Sub-item with.

Implementation Reference

  • Core implementation of the tool logic: calls monday_client.updates.create_update to add an update (comment) to the specified item.
    async def handle_monday_create_update_on_item(
        itemId: str,
        updateText: str,
        monday_client: MondayClient,
    ) -> list[types.TextContent]:
        monday_client.updates.create_update(item_id=itemId, update_value=updateText)
        return [
            types.TextContent(
                type="text", text=f"Created new update on Monday.com item: {updateText}"
            )
        ]
  • MCP tool registration for 'monday_create_update' (maps to 'monday-create-update'), includes input schema via type hints and docstring, wraps and calls the core handler.
    @mcp.tool()
    async def monday_create_update(itemId: str, updateText: str) -> str:
        """Create an update (comment) on a Monday.com Item or Sub-item.
    
        Args:
            itemId: Monday.com Item ID to create the update on.
            updateText: Content to update the Item or Sub-item with.
        """
        try:
            client = get_monday_client()
            result = await handle_monday_create_update_on_item(itemId, updateText, client)
            return result[0].text
        except Exception as e:
            return f"Error creating update: {e}"
  • Input schema documentation for the tool parameters.
    """Create an update (comment) on a Monday.com Item or Sub-item.
    
    Args:
        itemId: Monday.com Item ID to create the update on.
        updateText: Content to update the Item or Sub-item with.
    """
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. While 'create' implies a write operation, it doesn't specify permissions required, rate limits, whether updates are editable/deletable, or what happens on success/failure (e.g., returns an update ID). 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 front-loads the core action ('create an update') and specifies the target ('on a Monday.com Item or Sub-item'). There's no wasted verbiage, making it easy for an agent to parse quickly.

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 (a write operation with no annotations or output schema), the description is insufficient. It lacks details on behavioral traits, error handling, return values, and differentiation from siblings. While conciseness is good, completeness suffers for a mutation tool in a rich sibling 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 50% (only 'updateText' has a description), and the description adds no parameter-specific information beyond what's implied by the tool name. It doesn't clarify 'itemId' format (e.g., numeric ID) or provide examples for 'updateText'. With moderate schema coverage, the description doesn't compensate enough to elevate the score above baseline.

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 ('create') and resource ('update/comment on Monday.com Item or Sub-item'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'monday-get-item-updates' or 'monday-update-item', which would require more specific language about creating comments versus other types of updates.

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 an existing item), exclusions (e.g., not for board-level updates), or comparisons to sibling tools like 'monday-update-item' (which might modify item fields rather than add comments). This leaves the agent with minimal context for tool selection.

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