Skip to main content
Glama
de-Blanck

protonmail-mcp-server

by de-Blanck

List Proton Mail Emails

proton_list_emails
Read-onlyIdempotent

List emails in a folder, sorted newest first, with pagination support. Returns email summaries including subject, sender, and date.

Instructions

List emails in a folder, sorted newest first, with pagination support.

Returns email summaries (subject, from, date, snippet) — not full bodies. Use proton_get_email to read an individual email's full content.

Args:

  • folder (string): Mailbox folder path (default: 'INBOX')

  • limit (number): Maximum emails to return, 1–100 (default: 20)

  • offset (number): Skip this many emails for pagination (default: 0)

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

Returns: Paginated list of email summaries with total count and pagination metadata.

Examples:

  • "Show my latest emails" -> proton_list_emails({ folder: "INBOX" })

  • "What's in my Sent folder?" -> proton_list_emails({ folder: "Sent" })

  • "Show me the next page" -> proton_list_emails({ folder: "INBOX", offset: 20 })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderNoMailbox folder path (e.g., 'INBOX', 'Sent', 'Folders/Partnerships')INBOX
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 indicate readonly and idempotent. Description adds sorting order and pagination behavior, but does not elaborate further on rate limits or other constraints.

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?

Concise, front-loaded with purpose. Structured with Args/Returns/Examples. Every sentence is informative, no padding.

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?

Without output schema, the description explains return structure (email summaries, pagination metadata). Covers all aspects needed for a list tool with 4 optional parameters.

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%, baseline 3. Description adds context via examples and clarifies default values, but does not significantly extend parameter understanding beyond the 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 the tool lists emails in a folder, sorted newest first with pagination support. It differentiates from siblings by noting that full bodies require proton_get_email.

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 (for summaries) and when to use a sibling (proton_get_email for full bodies). Provides examples to illustrate usage.

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