Skip to main content
Glama
sakce

Monday.com MCP Server

by sakce

monday-move-item-to-group

Move a Monday.com item to a specified group within a board. Use this tool to organize and manage board items efficiently by specifying the item and group IDs.

Instructions

Move an item to a group in a Monday.com board

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupIdYesMonday.com Group ID to move the Item to.
itemIdYesMonday.com Item ID to move.

Implementation Reference

  • The handler function that executes the tool logic by calling monday_client.items.move_item_to_group to move the item to the specified group.
    async def handle_monday_move_item_to_group(
        monday_client: MondayClient, item_id: str, group_id: str
    ) -> list[types.TextContent]:
        """
        Move an item to a group in a Monday.com board.
    
        Args:
            monday_client (MondayClient): The Monday.com client.
            item_id (str): The ID of the item to move.
            group_id (str): The ID of the group to move the item to.
        """
        item = monday_client.items.move_item_to_group(item_id=item_id, group_id=group_id)
        return [
            types.TextContent(
                type="text",
                text=f"Moved item {item_id} to group {group_id}. ID of the moved item: {item['data']['move_item_to_group']['id']}",
            )
        ]
  • Registers the monday_move_item_to_group tool using @mcp.tool decorator, which wraps the core handler and handles client initialization and error wrapping.
    @mcp.tool()
    async def monday_move_item_to_group(itemId: str, groupId: str) -> str:
        """Move an item to a group in a Monday.com board.
    
        Args:
            itemId: Monday.com Item ID to move.
            groupId: Monday.com Group ID to move the Item to.
        """
        try:
            client = get_monday_client()
            result = await handle_monday_move_item_to_group(client, itemId, groupId)
            return result[0].text
        except Exception as e:
            return f"Error moving item: {e}"
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Move') but doesn't reveal critical traits such as whether this requires specific permissions, if it's reversible, potential side effects (e.g., impact on item data or board structure), or rate limits. 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, direct sentence that efficiently conveys the core action without any fluff or redundancy. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly. Every word earns its place by specifying the verb, object, and target.

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 details on behavioral traits (e.g., permissions, reversibility), usage context relative to siblings, and expected outcomes. While concise, it doesn't provide enough information for an agent to confidently invoke this tool in a real-world scenario.

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 input schema has 100% description coverage, with clear parameter descriptions for 'groupId' and 'itemId'. The description adds no additional semantic context beyond what the schema provides (e.g., it doesn't explain how to obtain these IDs or their format). According to the rules, with high schema coverage, the baseline is 3 even without param info in the description.

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 ('Move') and the resources involved ('an item to a group in a Monday.com board'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'monday-create-item' or 'monday-update-item', which also involve item manipulation, so it misses the highest score for sibling differentiation.

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. For example, it doesn't mention prerequisites like needing an existing item and group, or contrast with tools like 'monday-create-item' (for new items) or 'monday-update-item' (for modifying item properties without moving). This leaves the agent without context for selection among 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