Proton Mail Bridge MCP

Overview Schema Source Related Servers Discussions Admin

search_indexed_emails

Read-only

Search local email index offline without IMAP, using free-text and field filters like from, subject, label, and domain. Returns matching emails from the SQLite index.

Instructions

Search the local SQLite mailbox index without making any IMAP connection. Supports free-text and field shortcuts inline: from:alice@example.com, to:bob, subject:invoice, label:Archive, domain:acme.com. Use for fast, offline-capable searches when the index is populated. Prefer search_emails when you need live IMAP results or when the index is stale or empty. Prefer this over search_emails when the index is current. Use search_emails if messages were received after the last sync. Each email's attachments are metadata only (id/filename/contentType/size/disposition) — use list_attachments or get_email_by_id for full attachment detail.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	Recipient filter.
`from`	No	Sender filter.
`label`	No	Folder or label filter.
`limit`	No	Maximum results.
`query`	No	Free-text query across indexed metadata.
`dateTo`	No	Inclusive end date/time in ISO format.
`fields`	No	Trim each returned email to just these field names (e.g. ["subject","from","date"]) to save tokens on large result sets. id is always included. Accepts either an array or a comma-separated string. Omit to get the full object.
`folder`	No	Folder filter.
`isRead`	No	Read status filter.
`subject`	No	Subject filter.
`dateFrom`	No	Inclusive start date/time in ISO format.
`threadId`	No	Thread id filter.
`isStarred`	No	Starred status filter.
`mailboxRole`	No	Normalized mailbox role like Inbox, Sent, Archive, or Trash.
`senderDomain`	No	Sender domain filter such as example.com.
`hasAttachment`	No	Attachment filter.
`attachmentName`	No	Attachment filename filter.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.1.37Sep 23, 2026
- changedInput schema / properties / limit / default
```
Previous value: -100New value: +50
```

Changed4 schema fields changedv1.17.1Aug 15, 2026

changedInput schema / properties / fields / description

Previous value: -"Trim each returned email to just these field names (e.g. [\"subject\",\"from\",\"date\"]) to save tokens on large result sets. id is always included. Also accepts a comma-separated string. Omit to get the full object."New value: +"Trim each returned email to just these field names (e.g. [\"subject\",\"from\",\"date\"]) to save tokens on large result sets. id is always included. Accepts either an array or a comma-separated string. Omit to get the full object."

removedInput schema / properties / fields / items
```
Removed value: -{
-  "type": "string"
-}
```

addedInput schema / properties / fields / oneOf

Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "string"
+  }
+]

removedInput schema / properties / fields / type
```
Removed value: -"array"
```

Changed1 schema field changedv1.17.0Aug 12, 2026

addedInput schema / properties / fields

Added value: +{
+  "description": "Trim each returned email to just these field names (e.g. [\"subject\",\"from\",\"date\"]) to save tokens on large result sets. id is always included. Also accepts a comma-separated string. Omit to get the full object.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

First observedv0.1.0May 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses that the tool is offline (no IMAP connection) and that attachments are metadata-only, directing to list_attachments or get_email_by_id for full details. This adds meaningful behavioral context without contradicting annotations.

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 moderately long but every sentence earns its place: core purpose, usage routing, and attachment caveat are all front-loaded and succinctly phrased. No redundant fluff.

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 17-parameter tool with no output schema, the description covers usage context, offline behavior, and attachment limitations, and points to alternatives for full detail. The attachment metadata hint and fields parameter explanation provide sufficient context for correct invocation.

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 baseline is 3. The description adds value by documenting inline field shortcuts (e.g., from:alice@example.com) for the query parameter and clarifying the fields parameter's token-saving purpose, going beyond the schema's basic descriptions.

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 clearly states a specific verb and resource: 'Search the local SQLite mailbox index without making any IMAP connection.' It explicitly differentiates from search_emails by naming the live-IMAP alternative and describing the offline, index-based nature.

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?

The description provides explicit when-to-use and when-not-to-use guidance: prefer this when the index is current, use search_emails when live results are needed or the index is stale/empty, and use search_emails for messages after the last sync. It names the alternative tool directly.

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

Deploy Server

search_indexed_emails

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools