Skip to main content
Glama
sakce

Monday.com MCP Server

by sakce

monday-list-subitems-in-items

Retrieve all sub-items linked to specified Monday.com items using the MCP server to organize and manage board data efficiently.

Instructions

List all Sub-items of a list of Monday.com Items

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdsYes

Implementation Reference

  • Core handler function that builds and executes a GraphQL query to fetch subitems for the given item IDs using the MondayClient, formats the response as JSON text content.
    async def handle_monday_list_subitems_in_items(
        itemIds: list[str],
        monday_client: MondayClient,
    ) -> list[types.TextContent]:
        formatted_item_ids = ", ".join(itemIds)
        get_subitems_in_item_query = f"""query
            {{
                items (ids: [{formatted_item_ids}]) {{
                    subitems {{
                        id
                        name
                        parent_item {{
                            id
                        }}
                        updates {{
                            id
                            body
                        }}
                        column_values {{
                            id
                            text
                            value
                        }}
                    }}
                }}
            }}"""
        response = monday_client.custom._query(get_subitems_in_item_query)
    
        return [
            types.TextContent(
                type="text",
                text=f"Sub-items of Monday.com items {itemIds}: {json.dumps(response)}",
            )
        ]
  • MCP tool registration using @mcp.tool() decorator. Defines the tool name 'monday_list_subitems_in_items', input schema (itemIds: List[str]), docstring description, and calls the core handler.
    @mcp.tool()
    async def monday_list_subitems_in_items(itemIds: List[str]) -> str:
        """List all Sub-items of a list of Monday.com Items.
    
        Args:
            itemIds: List of Monday.com Item IDs to get sub-items for.
        """
        try:
            client = get_monday_client()
            result = await handle_monday_list_subitems_in_items(itemIds, client)
            return result[0].text
        except Exception as e:
            return f"Error listing sub-items: {e}"
  • Import of the handler function from item.py into fastmcp_server.py, necessary for tool registration.
    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,
    )
Behavior1/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the basic action without mentioning any behavioral traits such as permissions required, rate limits, pagination, error conditions, or what format the sub-items are returned in. This leaves critical operational context completely undocumented.

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, clear sentence that efficiently communicates the core purpose without any wasted words. It's appropriately sized for a simple list operation and front-loads the essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations, 0% schema coverage, and no output schema, the description is completely inadequate. It doesn't explain what sub-items are, how they're structured, what data is returned, or any operational constraints. For a tool with one undocumented parameter and no behavioral context, this provides far too little information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, meaning the single parameter 'itemIds' has no documentation in the schema. The description adds no information about this parameter—it doesn't explain what item IDs are, where to get them, format expectations, or constraints. With no parameter details in either schema or description, this is severely inadequate.

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 ('List all') and target resource ('Sub-items of a list of Monday.com Items'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'monday-get-items-by-id' or 'monday-list-items-in-groups' which also retrieve item-related data, so it falls short of 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?

The description provides no guidance on when to use this tool versus alternatives. With siblings like 'monday-get-items-by-id' and 'monday-list-items-in-groups' that handle similar item data, there's no indication of when sub-items specifically are needed or what prerequisites might exist for accessing them.

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