Skip to main content
Glama

archive_list

Archive a list in Remember The Milk to remove it from active view. Input the list name to archive and receive updated list details.

Instructions

Archive a list.

Args: list_name: Name of the list to archive

Returns: Updated list details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The archive_list tool handler. Looks up a list by name (case-insensitive), calls rtm.lists.archive API, and returns the archived list details with a transaction ID for undo support.
    async def archive_list(
        ctx: Context,
        list_name: str,
    ) -> dict[str, Any]:
        """Archive a list.
    
        Args:
            list_name: Name of the list to archive
    
        Returns:
            Updated list details
        """
        from ..client import RTMClient
    
        client: RTMClient = await get_client()
    
        lists_result = await client.call("rtm.lists.getList")
        lists = parse_lists_response(lists_result)
    
        list_id = None
        for lst in lists:
            if lst["name"].lower() == list_name.lower():
                list_id = lst["id"]
                break
    
        if not list_id:
            return build_response(data={"error": f"List not found: {list_name}"})
    
        result = await client.call(
            "rtm.lists.archive",
            require_timeline=True,
            list_id=list_id,
        )
    
        lst = result.get("list", {})
    
        return build_response(
            data={
                "list": format_list(lst),
                "message": f"Archived list: {list_name}",
            },
            transaction_id=get_transaction_id(result),
        )
  • The unarchive_list tool handler (inverse operation). Same lookup logic, calls rtm.lists.unarchive API.
    async def unarchive_list(
        ctx: Context,
        list_name: str,
    ) -> dict[str, Any]:
        """Unarchive a list.
    
        Args:
            list_name: Name of the list to unarchive
    
        Returns:
            Updated list details
        """
        from ..client import RTMClient
    
        client: RTMClient = await get_client()
    
        # Need to include archived lists in search
        lists_result = await client.call("rtm.lists.getList")
        lists = parse_lists_response(lists_result)
    
        list_id = None
        for lst in lists:
            if lst["name"].lower() == list_name.lower():
                list_id = lst["id"]
                break
    
        if not list_id:
            return build_response(data={"error": f"List not found: {list_name}"})
    
        result = await client.call(
            "rtm.lists.unarchive",
            require_timeline=True,
            list_id=list_id,
        )
    
        lst = result.get("list", {})
    
        return build_response(
            data={
                "list": format_list(lst),
                "message": f"Unarchived list: {list_name}",
            },
            transaction_id=get_transaction_id(result),
        )
  • The register_list_tools function that registers all list tools (including archive_list) via @mcp.tool() decorator. Called from server.py line 104.
    def register_list_tools(mcp: Any, get_client: Any) -> None:
        """Register all list-related tools."""
  • Registration call that wires register_list_tools into the MCP server, which in turn registers archive_list via the @mcp.tool() decorator inside lists.py.
    # Register all tools
    register_task_tools(mcp, get_client)
    register_list_tools(mcp, get_client)
    register_note_tools(mcp, get_client)
    register_utility_tools(mcp, get_client)
  • The format_list helper used by archive_list to format the response.
    def format_list(lst: dict[str, Any]) -> dict[str, Any]:
        """Format a list for response."""
        return {
            "id": lst.get("id"),
            "name": lst.get("name"),
            "smart": lst.get("smart") == "1",
            "archived": lst.get("archived") == "1",
            "locked": lst.get("locked") == "1",
        }
Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It fails to disclose what archiving entails (e.g., visibility changes, reversibility) or required permissions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and uses a structured Args/Returns format, but it is too terse and omits important context, sacrificing substance for brevity.

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?

For a simple tool with an output schema (not shown), the description covers the basic action and return value. However, it lacks behavioral context and usage guidance.

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

Parameters2/5

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

Schema description coverage is 0%, but the description only repeats the parameter name ('list_name') with minimal clarification. No additional details like format or validation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Archive') and resource ('list'), clearly indicating the action and target. It distinguishes from siblings like 'delete_list' and 'unarchive_list'.

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 on when to use vs alternatives such as 'delete_list' or 'unarchive_list'. No context about prerequisites or effects.

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

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/ljadach/rtm-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server