Skip to main content
Glama
Soundhannes

IMAP MCP Server

by Soundhannes
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_auto_archive_list

Retrieve the list of email senders configured for automatic archiving in your IMAP account to manage and review automated email organization rules.

Instructions

Get list of senders that are auto-archived

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/imap_mcp/imap_client.py:886-888 (handler)
    The implementation of the get_auto_archive_list method which returns the list of auto-archive senders from the IMAP client.
    def get_auto_archive_list(self) -> list[AutoArchiveSender]:
    """Get list of senders that are auto-archived."""
    return self.auto_archive_senders
  • src/imap_mcp/imap_client.py:886-888 (handler)
    The actual implementation of the get_auto_archive_list method within the IMAP client.
    def get_auto_archive_list(self) -> list[AutoArchiveSender]:
    """Get list of senders that are auto-archived."""
    return self.auto_archive_senders
  • src/imap_mcp/server.py:667-668 (registration)
    The MCP server request handler that dispatches the "get_auto_archive_list" tool call to the imap_client instance.
    elif name == "get_auto_archive_list":
    return imap_client.get_auto_archive_list()
  • src/imap_mcp/server.py:407-410 (registration)
    Registration of the get_auto_archive_list tool.
        "get_auto_archive_list",
    "Get list of senders that are auto-archived",
    {},
),
  • src/imap_mcp/server.py:667-668 (handler)
    The tool invocation handler that calls the IMAP client's get_auto_archive_list method.
    elif name == "get_auto_archive_list":
    return imap_client.get_auto_archive_list()

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action but lacks details on permissions, rate limits, side effects, or response format. For a read operation 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, efficient sentence that directly states the tool's purpose without any wasted words. It is front-loaded and appropriately sized for a simple tool, making it easy to parse quickly.

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. It doesn't explain what the returned list contains (e.g., sender details, format) or any behavioral aspects like error handling. For a tool with no structured data beyond the input schema, more context is needed to be fully helpful.

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

Parameters4/5

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

The input schema has 0 parameters with 100% coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter details, and it correctly implies no inputs are required, aligning with the schema. A baseline of 4 is appropriate as it doesn't contradict the schema.

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 'Get' and the resource 'list of senders that are auto-archived', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'reload_auto_archive' or 'process_auto_archive', which might involve similar concepts, so it doesn't reach 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. It doesn't mention prerequisites, context, or exclusions, such as whether it requires prior setup or differs from other list-related tools like 'list_mailboxes'. This leaves the agent with minimal usage direction.

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