Skip to main content
Glama
Soundhannes

IMAP MCP Server

by Soundhannes

add_auto_archive_sender

Automatically archive emails from specific senders or domains by adding them to an auto-archive list. This tool helps organize your inbox by filtering out emails you want archived automatically.

Instructions

Add sender to auto-archive list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesEmail address or domain to auto-archive
commentNoOptional comment/reason

Implementation Reference

  • The logic that adds an email sender to the auto-archive configuration list and saves the config to disk.
    def add_auto_archive_sender(
        self, email_addr: str, comment: Optional[str] = None
    ) -> bool:
        """Add sender to auto-archive list."""
        sender = AutoArchiveSender(
            email=email_addr,
            comment=comment,
            added_at=datetime.now(),
        )
        self.auto_archive_senders.append(sender)
        self._save_auto_archive_config()
        return True
  • The MCP server handler that dispatches calls to the 'add_auto_archive_sender' tool to the appropriate method in the IMAP client instance.
    elif name == "add_auto_archive_sender":
        return imap_client.add_auto_archive_sender(
            email_addr=args["email"],
            comment=args.get("comment"),
        )
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention if this is a mutation, requires specific permissions, has side effects, or how it interacts with other tools like 'get_auto_archive_list'. More context is needed for safe use.

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 no wasted words. It is front-loaded and directly states the tool's function, 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 complexity of a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'auto-archive' means, how the list is used, or what the tool returns, leaving gaps in understanding its role and effects.

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 has 100% description coverage, so parameters are well-documented in the schema itself. The description adds no additional meaning beyond implying the tool uses an email parameter, which aligns with the schema. 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 action ('Add') and resource ('sender to auto-archive list'), making the purpose understandable. However, it does not differentiate from its sibling 'remove_auto_archive_sender' or explain what 'auto-archive' entails, which prevents 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?

No guidance is provided on when to use this tool versus alternatives like 'process_auto_archive' or 'reload_auto_archive', nor does it mention prerequisites such as authentication or connection state. The description lacks context for effective tool selection.

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