Skip to main content
Glama
Soundhannes

IMAP MCP Server

by Soundhannes

list_mailboxes

Retrieve all mailbox folders from an IMAP email account to organize and manage email storage efficiently.

Instructions

List all mailbox folders

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
patternNoFilter pattern (optional)

Implementation Reference

  • Implementation of the 'list_mailboxes' tool in the IMAP client wrapper.
    def list_mailboxes(self, pattern: str = "*") -> list[MailboxInfo]:
        """List all mailbox folders."""
        self._ensure_connected()
        folders = self.client.list_folders(pattern=pattern)
        return [
            MailboxInfo(
                name=f[2],
                delimiter=f[1],
                flags=[str(flag) for flag in f[0]],
            )
            for f in folders
        ]
  • Registration/dispatching logic for 'list_mailboxes' in the MCP server implementation.
    elif name == "list_mailboxes":
        return imap_client.list_mailboxes(pattern=args.get("pattern", "*"))
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 it lists folders but doesn't mention whether this is a read-only operation, if it requires authentication, how results are returned (e.g., pagination), or any rate limits. This leaves significant gaps for a tool that likely interacts with a mail system.

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 with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly without unnecessary elaboration.

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 lack of annotations and output schema, the description is incomplete for a tool that lists folders. It doesn't explain what the output looks like (e.g., list of folder names, metadata), potential errors, or dependencies like needing to be connected first. This is inadequate for proper agent usage.

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%, so the schema already documents the optional 'pattern' parameter. The description adds no additional meaning about parameters beyond what's in the schema, such as examples of filter patterns or how they're applied. This meets the baseline for high schema coverage.

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 verb ('List') and resource ('all mailbox folders'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'select_mailbox' or 'get_mailbox_status', which also involve mailbox operations, so it doesn't reach the highest clarity level.

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 many sibling tools like 'select_mailbox' or 'get_mailbox_status' that might overlap in mailbox-related contexts, there's no explicit or implied direction on usage scenarios or exclusions.

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/Soundhannes/IMAP-MCP'

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