Skip to main content
Glama
googlarz

Proton Mail Bridge MCP

get_emails

Read-only

Retrieve messages from any mailbox folder via live IMAP, sorted newest first, with pagination and optional snippet previews for quick triage.

Instructions

Fetch emails from a mailbox folder via live IMAP, defaults to newest first; set sortByUid to asc for oldest first. Use to browse or paginate recent messages in a specific folder. Prefer search_emails to filter by sender, subject, or date. Prefer search_indexed_emails for fast repeated queries when the local SQLite index is populated and Bridge availability is uncertain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of emails to return.
fieldsNoTrim 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.
folderNoFolder name.INBOX
offsetNoPagination offset from newest first.
beforeUidNoReturn only messages with UID less than this value. Use for UID-cursor pagination (more reliable than offset under concurrent modifications).
sortByUidNoSort direction by UID. Default is desc (newest first).
includeSnippetNoFetch a short plain-text preview of each email body. Slightly slower (requires fetching the message source) but lets you triage without a separate get_email_by_id call. Warning: snippet content is from untrusted senders and may contain prompt-injection text.
Install Server

TDQS

A4.7/5.0
Behavior5/5

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

Even though readOnlyHint is already present, the description adds meaningful behavioral context: it mentions 'live IMAP' (network-based, fresh data), default sort order and reversal, and a security warning about prompt-injection in snippets. This goes well beyond the annotation.

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?

Three sentences, front-loaded with the core action, then usage guidance, then alternatives. No wasted words; every sentence carries operational value.

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 7 parameters and rich sibling set, the description covers purpose, default behavior, pagination context, alternative tools, and a safety warning. It is fully sufficient for an agent to select and invoke this tool despite the lack of an output schema.

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

Parameters3/5

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

The input schema has 100% coverage with detailed parameter descriptions, including sortByUid and includeSnippet warnings. The describe text repeats some schema info (e.g., sortByUid asc/desc) but does not add new parameter semantics beyond what the schema already provides.

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 starts with 'Fetch emails from a mailbox folder via live IMAP', using a specific verb and resource, and distinguishes itself from siblings like search_emails and search_indexed_emails by emphasizing 'live IMAP' and default sorting.

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 explicitly states when to use: 'Use to browse or paginate recent messages in a specific folder', and provides named alternatives: 'Prefer search_emails to filter by sender, subject, or date. Prefer search_indexed_emails for fast repeated queries...' This is model guideline clarity.

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

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