Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_move

Move an email from one folder to another across Gmail, Outlook, iCloud, or IMAP accounts, with source folder support when the message is not in INBOX.

Instructions

Move an email to a different folder

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": {
      "accountId": "<accountId>",
      "emailId": "<emailId>",
      "targetFolder": "<targetFolder>"
    },
    "name": "email_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailIdYes
accountIdYes
sourceFolderNoSource folder (required for IMAP/iCloud when email is not in INBOX)
targetFolderYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and delivers almost nothing: it doesn't say whether the email is copied or removed from the source, what happens to folder membership/labels, whether failures are atomic, or what permissions are required. Only the implicit fact that this mutates state can be inferred from the verb 'Move'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero wasted words. The terseness is a specification gap rather than a stylistic flaw, so it scores well here but not perfectly.

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 4 parameters, no annotations, and no output schema, the definition is far too thin. An agent cannot learn the conditional sourceFolder requirement, identifier formats, or expected outcome from it, which risks malformed calls on non-INBOX IMAP moves.

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

Parameters2/5

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

Schema description coverage is only 25% (just sourceFolder), and the description adds nothing about accountId, emailId, or targetFolder formats, nor the conditional sourceFolder requirement. With a low-coverage schema, the description should compensate but instead reiterates only the title-level behavior.

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?

States a specific verb (move) and resource (email -> folder), so the operation is unambiguous. It does not distinguish itself from the sibling email_batch_move, which an agent could easily confuse it with for multi-message work.

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?

There is no when-to-use or when-not-to-use guidance, no mention of the batch alternative for moving multiple messages, and no prerequisites. The only usage hint in the whole definition (sourceFolder needed for IMAP/iCloud when not in INBOX) lives in the schema, not the description.

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