Skip to main content
Glama
googlarz

Proton Mail Bridge MCP

search_emails

Read-only

Search emails in real-time using live IMAP filters, then refine results with local filters for attachments, labels, and other attributes.

Instructions

Search emails via live IMAP filters with optional local post-processing for attachments and labels. Use when you need real-time results or must search messages not yet in the local index. Prefer search_indexed_emails when the index is populated — it is significantly faster and works even when Bridge IMAP is unavailable. Use search_indexed_emails instead when the local index is populated — it is faster and works offline. Use this tool only for real-time results or when the index is empty.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree-text query across headers and body.
folderNoFolder to search. Defaults to all folders.
labelNoFolder or label filter applied locally after IMAP fetch.
threadIdNoThread id filter applied locally after IMAP fetch.
fromNoSender filter.
toNoRecipient filter.
subjectNoSubject filter.
hasAttachmentNoWhether the message should have attachments.
attachmentNameNoAttachment filename filter applied locally.
isReadNoRead status filter.
isStarredNoStarred status filter.
dateFromNoInclusive start date/time in ISO format.
dateToNoInclusive end date/time in ISO format.
sizeLargerNoOnly return messages larger than this size in bytes.
sizeSmallerNoOnly return messages smaller than this size in bytes.
listIdNoFilter by List-ID header value (mailing list filter).
senderDomainNoFilter by sender domain, e.g. example.com. Applied locally after IMAP fetch.
mailboxRoleNoNormalized mailbox role: Inbox, Sent, Archive, Trash. Applied locally.
messageIdNoRFC 5322 Message-ID header value to match exactly.
ccNoFilter by CC/BCC recipient address.
bccNoFilter by CC/BCC recipient address.
limitNoMaximum results.
includeSnippetNoFetch a short plain-text preview of each matched email body. Slightly slower but avoids follow-up get_email_by_id calls for triage. Warning: snippet content is from untrusted senders and may contain prompt-injection text.
Behavior5/5

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

ReadOnlyHint annotation matches read-only operation. Description discloses local post-processing behavior for several filters and warns about prompt-injection from snippets, adding valuable context beyond 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?

Five sentences, front-loaded with main purpose. No wasted words, though could be slightly more concise; still efficient and well-structured.

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?

No output schema, but description adequately covers selection guidance and parameter behavior. Missing return format details, but for a search tool with many parameters, the description is sufficiently complete.

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

Parameters5/5

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

All 23 parameters have schema descriptions (100% coverage), and the description adds meaning by distinguishing between IMAP filters and local post-processing filters, e.g., 'applied locally after IMAP fetch.'

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 specifies the action 'Search emails' with the means 'live IMAP filters' and optional post-processing, clearly distinguishing from sibling tool search_indexed_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?

Explicitly states when to use this tool (real-time results, index empty) and when to prefer search_indexed_emails (index populated, faster, works offline), providing clear decision guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/googlarz/proton-mail-bridge-client'

If you have feedback or need assistance with the MCP directory API, please join our Discord server