Skip to main content
Glama
sakce

Monday.com MCP Server

by sakce

monday-get-items-by-id

Retrieve specific items from Monday.com using their unique IDs. This tool simplifies data access by allowing users to fetch precise information directly from their boards.

Instructions

Fetch specific Monday.com item by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemIdYesID of the Monday.com item to fetch.

Implementation Reference

  • The primary handler function for the 'monday_get_items_by_id' tool (likely 'monday-get-items-by-id' in kebab case), decorated with @mcp.tool(). It wraps the internal helper by calling get_monday_client() and handle_monday_get_item_by_id.
    @mcp.tool()
    async def monday_get_items_by_id(itemId: str) -> str:
        """Fetch specific Monday.com item by its ID.
    
        Args:
            itemId: ID of the Monday.com item to fetch.
        """
        try:
            client = get_monday_client()
            result = await handle_monday_get_item_by_id(itemId, client)
            return result[0].text
        except Exception as e:
            return f"Error fetching item: {e}"
  • Internal helper function that implements the core logic: fetches item(s) by ID using monday_client.items.fetch_items_by_id and formats the response as TextContent.
    async def handle_monday_get_item_by_id(
        itemId: str,
        monday_client: MondayClient,
    ) -> list[types.TextContent]:
        """Fetch specific Monday.com items by their IDs"""
        try:
            response = monday_client.items.fetch_items_by_id(ids=itemId)
    
            return [
                types.TextContent(
                    type="text",
                    text=f"Monday.com items: {json.dumps(response)}",
                )
            ]
        except Exception as e:
            return [
                types.TextContent(
                    type="text",
                    text=f"Error fetching Monday.com items: {e}",
                )
            ]
Behavior2/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 states this is a fetch operation, implying read-only behavior, but doesn't clarify authentication requirements, rate limits, error handling, or what happens if the ID doesn't exist. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 gets straight to the point with no wasted words. It's appropriately sized for a simple fetch 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.

Completeness3/5

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

Given the tool's simplicity (single parameter, no output schema, no annotations), the description is minimally adequate but incomplete. It doesn't address behavioral aspects like authentication or error handling, and while the schema covers the parameter, the description doesn't help differentiate this tool from similar siblings. For a basic fetch tool, it meets minimum requirements but could be more helpful.

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%, with the single parameter 'itemId' clearly documented in the schema. The description adds no additional parameter information beyond what's already in the structured schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no 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 ('Fetch') and resource ('specific Monday.com item'), making the purpose immediately understandable. However, it doesn't differentiate this tool from other item-fetching siblings like 'monday-list-items-in-groups' or 'monday-list-subitems-in-items', which would require specifying that this retrieves a single item by ID rather than listing multiple items.

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-list-items-in-groups' and 'monday-list-subitems-in-items' that also retrieve items, there's no indication that this tool is specifically for fetching a single item by ID rather than listing items by other criteria. No exclusions or prerequisites are mentioned.

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