Skip to main content
Glama
Soundhannes

IMAP MCP Server

by Soundhannes
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

copy_email

Copy selected emails from one mailbox to another in IMAP accounts. Specify source emails by UID and destination mailbox to organize messages.

Instructions

Copy emails to another mailbox

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidsYesEmail UIDs
destinationYesDestination mailbox
mailboxNoSource mailbox (default: current)

Implementation Reference

  • src/imap_mcp/imap_client.py:665-673 (handler)
    The `copy_email` method in `imap_client.py` handles the logic for copying emails between IMAP mailboxes.
    def copy_email(
    self, uids: list[int], destination: str, mailbox: Optional[str] = None
) -> bool:
    """Copy emails to another mailbox."""
    self._ensure_connected()
    if mailbox:
        self.select_mailbox(mailbox)
    self.client.copy(uids, destination)
    return True
  • src/imap_mcp/server.py:614-619 (registration)
    The `copy_email` tool is registered and handled within the main server loop in `src/imap_mcp/server.py`.
    elif name == "copy_email":
    return imap_client.copy_email(
        uids=args["uids"],
        destination=args["destination"],
        mailbox=args.get("mailbox"),
    )

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 the full burden of behavioral disclosure. It states the action ('copy emails') but does not clarify whether this creates duplicates, preserves originals, requires specific permissions, or has side effects like updating timestamps. For a mutation tool with zero annotation coverage, this leaves critical behavioral traits unspecified.

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 unnecessary words. It is front-loaded with the core action, making it easy for an agent to parse quickly and accurately.

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 insufficient. It lacks details on behavioral outcomes (e.g., whether copying affects original emails, error conditions, or return values), leaving the agent with incomplete context to invoke the tool safely and effectively.

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 description coverage is 100%, with clear descriptions for all three parameters (uids, destination, mailbox). The description adds no additional semantic context beyond what the schema provides, such as format examples or constraints, so it meets the baseline for adequate but unenhanced parameter documentation.

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 ('copy') and resource ('emails'), specifying the action of moving emails to another mailbox. However, it does not differentiate from sibling tools like 'move_email' or 'archive_email', which perform similar relocation operations but with different behavioral implications.

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 such as 'move_email' or 'archive_email'. The description lacks context about prerequisites (e.g., needing authentication or selecting a mailbox first) or exclusions, leaving the agent to infer usage from the tool name alone.

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