Skip to main content
Glama
sethbang

proton-mail-mcp

list_messages

Read-onlyIdempotent

List recent messages from an email folder, sorted by date or UID. Returns subject, sender, date, and flags with optional body preview.

Instructions

List recent messages from an email folder, sorted by date (newest first). Returns subject, sender, date, and flags for each message. A non-selectable namespace container (e.g. Folders/Labels) is rejected with an actionable error rather than returning an empty list.

Pagination note: the default date sort is paginated by a UID cursor (beforeUid). In folders where UID order disagrees with date order — All Mail, or any folder holding moved messages — page boundaries can skip or reorder messages relative to strict date order. For exact, skip-free paging set sortByUid: true (orders by UID = arrival order, newest first); for a precise date window use search_messages with since/before.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderNoFolder path to list messages from (default: INBOX)INBOX
limitNoMaximum number of messages to return (default: 20, max: 100)
beforeUidNoFetch messages with UIDs before this value (for pagination). Pass the smallest UID from the previous page.
includeSnippetNoAppend a ~200-char body preview to each row. Adds one fetch per message; default off.
sortByUidNoOrder by UID descending (arrival order, newest first) instead of by date. Makes `beforeUid` pagination exact — no skips or duplicates at page boundaries, even in All Mail or folders with moved messages. Default false (date sort).
Behavior5/5

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

Annotations indicate readOnlyHint and idempotentHint. The description adds detailed behavioral context: date sort default, pagination mechanics, potential skips/duplicates in certain folders, and the error behavior for namespace containers. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured: first sentence states core purpose and output, then error behavior, then a detailed pagination note. No fluff; every sentence adds value. Uses bold for key terms.

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 5 parameters (all well-described in schema), no output schema, and 29 siblings, the description covers main functionality, pagination nuances, and edge cases (namespace error). It provides sufficient context for an agent to use the tool correctly.

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 3. The description adds meaning beyond schema: explains that sortByUid makes beforeUid pagination exact, includeSnippet adds a body preview, and default sorting is by date newest first. This extra context warrants a 4.

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 recent messages from a folder, sorted by date, and specifies returned fields (subject, sender, date, flags). It also distinguishes from siblings like search_messages by mentioning when to use that tool for date windows.

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 provides explicit guidance on pagination: when to use beforeUid, when to set sortByUid for exact paging, and when to use search_messages for precise date windows. It also warns about namespace containers causing errors.

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/sethbang/proton-mail-mcp'

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