Skip to main content
Glama
de-Blanck

protonmail-mcp-server

by de-Blanck

Search Proton Mail Emails

proton_search_emails
Read-onlyIdempotent

Search emails in a specified folder using filters like sender, subject, date range, read status, and flagged status. Returns paginated summaries for quick scanning.

Instructions

Search emails in a folder using IMAP search criteria. Supports filtering by sender, recipient, subject, body text, date range, and read/flagged status.

Returns email summaries — use proton_get_email to read the full content of a specific result.

Args:

  • folder (string): Folder to search in (default: 'INBOX')

  • from (string, optional): Filter by sender email or name

  • to (string, optional): Filter by recipient email or name

  • subject (string, optional): Filter by subject text

  • body (string, optional): Search within email body

  • since (string, optional): Emails after this date (ISO 8601, e.g., '2025-01-01')

  • before (string, optional): Emails before this date (ISO 8601)

  • unseen (boolean, optional): Only unread emails

  • flagged (boolean, optional): Only starred/flagged emails

  • limit (number): Max results, 1–100 (default: 20)

  • offset (number): Pagination offset (default: 0)

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: Paginated list of matching email summaries.

Examples:

  • "Find emails from Alice" -> proton_search_emails({ from: "Alice" })

  • "Unread emails about quarterly report" -> proton_search_emails({ subject: "quarterly report", unseen: true })

  • "Emails from acme.com in March" -> proton_search_emails({ from: "acme.com", since: "2025-03-01", before: "2025-04-01" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderNoMailbox folder to search in (e.g., 'INBOX', 'Sent')INBOX
fromNoFilter by sender email or name (partial match)
toNoFilter by recipient email or name (partial match)
subjectNoFilter by subject line (partial match)
bodyNoSearch within email body text
sinceNoOnly emails after this date (ISO 8601, e.g., '2025-01-01')
beforeNoOnly emails before this date (ISO 8601, e.g., '2025-04-01')
unseenNoIf true, only return unread emails
flaggedNoIf true, only return flagged/starred emails
limitNoMaximum emails to return (1–100, default 20)
offsetNoNumber of results to skip for pagination
response_formatNoOutput format: 'markdown' for human-readable or 'json' for structured datamarkdown
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds behavioral context: returns summaries, supports pagination (limit, offset), and default folder is INBOX. No contradictions.

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?

Well-structured with intro, parameter list, and examples. Slightly long due to full parameter listing, but clear and front-loaded with purpose.

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 12 parameters and no output schema, description explains all inputs, return type (paginated summaries), and usage examples. Sufficient for an AI agent.

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 explaining defaults, date format (ISO 8601), and response_format enum meanings, going beyond schema.

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 it searches emails in a folder using IMAP search criteria, listing specific filters. It distinguishes itself from siblings like proton_get_email by noting that full content retrieval requires a separate tool.

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 mentions when to use this tool (for searching/filtering) and when to use a sibling (proton_get_email for full content). Provides examples for common queries.

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/de-Blanck/protonmail-mcp-server'

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