Skip to main content
Glama
sakce

Monday.com MCP Server

by sakce

monday-delete-item

Remove a specific item from a Monday.com board by providing its unique item ID. This tool facilitates efficient item management within the Monday.com MCP Server.

Instructions

Delete an item from a Monday.com board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdYesMonday.com Item ID to delete.

Implementation Reference

  • Core handler function that performs the item deletion using the MondayClient API.
    async def handle_monday_delete_item(
        monday_client: MondayClient, item_id: str
    ) -> list[types.TextContent]:
        """
        Delete an item from a Monday.com board.
    
        Args:
            monday_client (MondayClient): The Monday.com client.
            item_id (str): The ID of the item to delete.
        """
        monday_client.items.delete_item_by_id(item_id=item_id)
        return [types.TextContent(type="text", text=f"Deleted item {item_id}.")]
  • Registers the tool 'monday_delete_item' (corresponding to 'monday-delete-item') with FastMCP, wrapping the core handler and defining input schema via args and docstring.
    @mcp.tool()
    async def monday_delete_item(itemId: str) -> str:
        """Delete an item from a Monday.com board.
    
        Args:
            itemId: Monday.com Item ID to delete.
        """
        try:
            client = get_monday_client()
            result = await handle_monday_delete_item(client, itemId)
            return result[0].text
        except Exception as e:
            return f"Error deleting item: {e}"
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool deletes an item, implying a destructive mutation, but fails to mention critical details like whether deletion is permanent, requires specific permissions, or has rate limits. This leaves significant gaps for safe agent operation.

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 is appropriately sized and front-loaded, making it easy 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 destructive nature, lack of annotations, and no output schema, the description is incomplete. It should address behavioral risks, alternatives, and expected outcomes to adequately guide an AI agent in a mutation-heavy environment with siblings like archive and update tools.

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 the single parameter 'itemId' documented as 'Monday.com Item ID to delete.' The description adds no additional meaning beyond this, such as format examples or sourcing instructions, so it meets the baseline for adequate but not enhanced parameter semantics.

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 ('Delete') and resource ('an item from a Monday.com board'), making the purpose immediately understandable. It doesn't distinguish from siblings like 'monday-archive-item' or 'monday-update-item', which would require explicit differentiation to achieve 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?

No guidance is provided on when to use this tool versus alternatives like 'monday-archive-item' or 'monday-update-item'. The description lacks context about prerequisites, such as needing an existing item ID, or warnings about irreversible deletion versus archiving.

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