Skip to main content
Glama
Soundhannes

IMAP MCP Server

by Soundhannes
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

remove_auto_archive_sender

Remove an email address from the automated archiving list to stop messages from that sender from being automatically archived.

Instructions

Remove sender from auto-archive list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesEmail address to remove

Implementation Reference

  • src/imap_mcp/imap_client.py:903-909 (handler)
    The actual implementation of the tool logic that removes a sender from the auto-archive list and saves the configuration.
    def remove_auto_archive_sender(self, email_addr: str) -> bool:
    """Remove sender from auto-archive list."""
    self.auto_archive_senders = [
        s for s in self.auto_archive_senders if s.email != email_addr
    ]
    self._save_auto_archive_config()
    return True
  • src/imap_mcp/server.py:420-427 (schema)
    MCP tool schema definition for remove_auto_archive_sender.
    make_tool(
    "remove_auto_archive_sender",
    "Remove sender from auto-archive list",
    {
        "email": {"type": "string", "description": "Email address to remove"},
    },
    ["email"],
),
  • src/imap_mcp/server.py:674-676 (registration)
    Tool handler dispatching to the imap_client method.
    elif name == "remove_auto_archive_sender":
    return imap_client.remove_auto_archive_sender(
        email_addr=args["email"],

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits such as whether this requires specific permissions, if it's reversible, what happens on success/failure, or any rate limits. This leaves significant gaps for a mutation tool.

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, direct sentence with zero waste—it efficiently conveys the core action without unnecessary words. It's appropriately sized and front-loaded for quick understanding.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, error conditions, or side effects, leaving the agent with insufficient context to use it effectively beyond the basic action.

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 input schema fully documents the 'email' parameter. The description adds no additional meaning beyond implying the email must be in the auto-archive list, which is minimal value. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('Remove') and resource ('sender from auto-archive list'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_auto_archive_list' or 'reload_auto_archive', 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 'get_auto_archive_list' for checking the list or 'process_auto_archive' for related operations. The description lacks context about prerequisites (e.g., needing the sender to be in the list first) 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