Selfhost-Remote-Mail-MCP

action

Manage email organization by ID. Move messages to specific folders, archive them, or classify them as spam, seen, or done.

Instructions

Sort or flag emails by ID: archive, markAsDone (= archive), moveToInbox, moveToTrash, moveToFolder (needs folder; a plain name means that folder in the email's own mailbox), markAsSpam, markAsSeen, markAsUnseen, pin, unpin, or unsubscribe (only shows the unsubscribe link or address; nothing is clicked or sent). Nothing is deleted for good; moved emails get new IDs, so list the folder again. A read-only mailbox refuses. Returns a short confirmation. To send a draft use send_email; to remove a draft use draft(delete).

Input Schema

TableJSON Schema

Name	Required	Description
`folder`	No	For moveToFolder: the folder to move them to.
`action_name`	Yes	What to do: archive, markAsDone, moveToInbox, moveToTrash, moveToFolder, markAsSpam, markAsSeen, markAsUnseen, pin, unpin or unsubscribe.
`message_ids`	Yes	The emails' IDs, like ['INBOX#1234'].

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 21, 2026

addedInput schema / properties / action_name / description

Added value: +"What to do: archive, markAsDone, moveToInbox, moveToTrash, moveToFolder, markAsSpam, markAsSeen, markAsUnseen, pin, unpin or unsubscribe."

addedInput schema / properties / folder / description

Added value: +"For moveToFolder: the folder to move them to."

addedInput schema / properties / message_ids / description
```
Added value: +"The emails' IDs, like ['INBOX#1234']."
```

First observedv0.19.1Oct 20, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds substantial behavior beyond the annotations: it clarifies that nothing is permanently deleted, moved emails receive new IDs so the folder must be re-listed, read-only mailboxes refuse the action, and unsubscribe does not click or send anything. These details align with destructiveHint=false and provide useful operational context. It also discloses that the tool returns a short confirmation.

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 front-loaded with the core purpose and then lists actions and caveats efficiently. Despite being dense, every sentence contributes operational meaning, especially the action aliases, folder semantics, and safety notes.

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

Completeness5/5

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

Given the presence of an output schema and annotations, the description is complete enough for correct invocation. It covers behavior, parameter nuances, safety constraints, and alternatives to sibling tools, leaving no significant gap for an agent selecting or calling this tool.

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

Parameters4/5

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

Schema coverage is already 100%, so all three parameters have structured descriptions. The description still adds value by explaining that markAsDone is equivalent to archive and that a plain folder name for moveToFolder means that folder within the email's own mailbox. It does not add much about message_ids beyond the schema, but the extra action and folder semantics justify above baseline.

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 opens with a specific verb and resource: "Sort or flag emails by ID," then enumerates every action the tool supports. Despite the generic tool name "action," an agent can distinguish this from siblings like send_email and draft based on the mutation-focused email operations listed.

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

Usage Guidelines4/5

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

The description gives clear context for when to use specific actions, including that moveToFolder needs a folder and that unsubscribe only reveals the unsubscribe link/address. It also names alternatives for drafts: send_email for sending and draft(delete) for removing. It does not cover every sibling relationship, but the guidance is strong and actionable.

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

Deploy Server