Selfhost-Remote-Mail-MCP

search

Read-only

Locate emails across multiple folders and mailboxes using keywords or Gmail-style filters, retrieving newest matches or paged lists.

Instructions

Search emails across many folders at once: by default every folder of the first mailbox except Trash and Spam; scope="all" covers every mailbox this app may use, a mailbox address or name all its folders, or give one folder. With query: keyword search returning the 20 newest matches with their text (cut at 3,000 characters; thread has the rest), best for questions about a topic. Without query: a paged list, one line per email, matching filter (same syntax as emails). To page through one folder use emails. Changes nothing.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Which page of results, starting at 1.
`order`	No	descending (newest first) or ascending (oldest first).	descending
`query`	No	Keywords to search for. Returns up to 20 newest matches with full bodies. Leave empty to list emails matching filter instead.
`scope`	No	Where to look: 'all' for every mailbox this app may use, a mailbox address or name for all its folders, or one folder. Empty means the first mailbox, without Trash and Spam.
`filter`	No	Gmail-style filter, can combine: from:, to:, cc:, subject:, before:yyyy/MM/dd, after:yyyy/MM/dd, newer_than:7d (d/w/m/y), older_than:, is:unread, is:read, is:starred, is:answered, has:attachment, filename:<name>, plain words, and -term to exclude.
`page_size`	No	How many emails per page.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 21, 2026

addedInput schema / properties / filter / description

Added value: +"Gmail-style filter, can combine: from:, to:, cc:, subject:, before:yyyy/MM/dd, after:yyyy/MM/dd, newer_than:7d (d/w/m/y), older_than:, is:unread, is:read, is:starred, is:answered, has:attachment, filename:<name>, plain words, and -term to exclude."

addedInput schema / properties / order / description

Added value: +"descending (newest first) or ascending (oldest first)."

addedInput schema / properties / page / description

Added value: +"Which page of results, starting at 1."

addedInput schema / properties / page_size / description
```
Added value: +"How many emails per page."
```

addedInput schema / properties / query / description

Added value: +"Keywords to search for. Returns up to 20 newest matches with full bodies. Leave empty to list emails matching filter instead."

addedInput schema / properties / scope / description

Added value: +"Where to look: 'all' for every mailbox this app may use, a mailbox address or name for all its folders, or one folder. Empty means the first mailbox, without Trash and Spam."

First observedv0.19.1Oct 20, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, and the description adds important behavior beyond that: default scope excludes Trash and Spam, scope='all' covers every accessible mailbox, query mode returns the 20 newest matches with text cut at 3,000 characters, and the rest of a thread is available elsewhere. It also explicitly states 'Changes nothing', reinforcing the read-only nature.

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?

The description is dense and front-loaded with the core behavior and modes. Every sentence carries useful information, but the single-paragraph structure and long sentences make it slightly harder to scan than ideal.

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 covers what an agent needs: search semantics, scope defaults, query vs. list behavior, result formatting, and the relevant alternative for one-folder paging. No critical invocation details are missing.

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 100%, so the schema already documents all parameters. The description adds meaningful semantics for query, scope, and filter beyond the schema, though it does not further explain page, order, or page_size. The added context for the key behavioral parameters is substantial.

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 states a specific verb and resource: search emails across many folders at once. It clearly distinguishes two operating modes (with query vs. without query) and explicitly routes single-folder paging to the sibling tool emails.

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

Usage Guidelines5/5

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

It gives explicit guidance on when to use the tool: with query for topic questions, without query for a paged list matching a filter. It also defines scope defaults and directs users to emails for paging through one folder, naming the relevant alternative.

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

Deploy Server