Skip to main content
Glama
googlarz

Proton Mail Bridge MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_emails

Read-only

Fetch and paginate mailbox emails from a Proton Mail folder via IMAP, newest first. Trim fields or include snippets to triage messages without extra calls.

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. 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
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.17.1
    • 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"
  2. Changed1 schema field changedv1.17.0
    • 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"
+}
  3. Addedv1.13.11
  4. Removedv1.13.11
  5. Changed3 schema fields changedv1.13.4
    • addedInput schema / properties / beforeUid
      Added value: +{
+  "description": "Return only messages with UID less than this value. Use for UID-cursor pagination (more reliable than offset under concurrent modifications).",
+  "type": "number"
+}
    • addedInput schema / properties / includeSnippet
      Added value: +{
+  "default": false,
+  "description": "Fetch 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.",
+  "type": "boolean"
+}
    • addedInput schema / properties / sortByUid
      Added value: +{
+  "description": "Sort direction by UID. Default is desc (newest first).",
+  "enum": [
+    "asc",
+    "desc"
+  ],
+  "type": "string"
+}
  6. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, and the description adds contextual behavior such as live IMAP access (implying network dependency), default sorting behavior, and the warning about prompt-injection risk in snippets. It also discloses that attachments are metadata-only. This adds meaningful behavioral insight beyond the annotation without contradicting it.

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 dense but well-organized: it opens with the core purpose and default behavior, then gives usage guidance, and finally addresses attachment handling and parameter details. While it is longer than a minimal description, every sentence adds functional value and it is front-loaded with the most critical information.

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?

Given the tool's complexity (7 parameters, no output schema), the description covers pagination strategies, alternative tools, attachment limitations, and a security warning. It does not explicitly describe the full return shape, but the schema and the mention of fields trimming give the agent enough context to call the tool correctly. The lack of an output schema is partially mitigated by the description's clarity on what is returned.

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?

With 100% schema description coverage, the baseline is 3. The description adds value by explaining the effect of sortByUid (asc for oldest first), the purpose of beforeUid for UID-cursor pagination, and the security caution for includeSnippet. These details go beyond the schema's basic descriptions, helping the agent use parameters more effectively.

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 fetches emails from a mailbox folder via live IMAP, specifies the default sorting order, and explicitly differentiates itself from siblings by noting that search_emails and search_indexed_emails are for filtering. It also mentions that full attachment details require list_attachments or get_email_by_id, preventing confusion with those tools.

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 gives explicit guidance on when to use this tool (browse or paginate recent messages in a folder) and when to prefer alternatives (search_emails for filtering, search_indexed_emails for fast repeated queries). It also advises using list_attachments or get_email_by_id for full attachment details, leaving no ambiguity about the tool's role.

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

Deploy Server

Other Tools