Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_transfer

Move or copy emails between accounts while preserving the original sender, date, and threading; optionally trash the source copy only after a confirmed import for safe cross-account transfers.

Instructions

Move or copy emails BETWEEN accounts, preserving the original message intact (sender, date, threading) by transferring the raw MIME. Fetches each message from the source account and imports it into the target account. With deleteAfter=true the source copy is sent to trash only after a confirmed import, making this a safe cross-account move.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sourceAccountId": "<sourceAccountId>",
      "targetAccountId": "<targetAccountId>",
      "emailIds": "<emailIds>"
    },
    "name": "email_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailIdsYesSource email IDs to transfer
markReadNoMark imported messages as read in the target. Default: provider default (usually unread).
deleteAfterNoSend the source copy to trash after a successful import. Default false (copy, leaving the original in place).
sourceFolderNoSource folder (required for IMAP/iCloud when emails are not in INBOX)
targetFolderNoDestination folder/label in the target account (Gmail label id or name; IMAP/Outlook folder name). Defaults to INBOX.
sourceAccountIdYesAccount to read messages from
targetAccountIdYesAccount to import messages into

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses fidelity guarantees (sender, date, threading preserved via raw MIME), the two-phase fetch-then-import flow, and that deletion is gated on a confirmed import. It does not cover partial-failure behavior for a multi-message batch, provider-side quirks, or any permission requirements, which keeps it below a 5.

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?

Three tight sentences, front-loaded with the core action and scope, followed by mechanism and then the safety semantics of the one most consequential flag. No filler or restatement of the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter cross-account mutation with no annotations and no output schema, the description covers the important semantics (fidelity, sequencing, destructive behavior). It leaves gaps on what is returned (per-message success counts) and on batch partial-failure handling, which an agent would need for a 1,000-message transfer.

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 explains sourceAccountId, targetAccountId, emailIds, sourceFolder, targetFolder, and markRead. The description adds only framing around deleteAfter (trash only after confirmed import = safe move), which is useful but already largely implied by the schema text; markRead and folder parameters get no added meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb pair ('move or copy') and a precise scope ('BETWEEN accounts'), which distinguishes it from the same-account email_move and email_batch_move siblings. The mechanism (raw MIME transfer) is also stated, so an agent knows exactly what the operation does without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: cross-account transfer with deleteAfter=true meaning a move and the default meaning a copy. There is no explicit routing guidance such as when to prefer this over email_move/email_batch_move, and no mention that both source and target accounts must already be registered (see email_add_account).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.