Skip to main content
Glama
RndmJoker

proton-mcp

by RndmJoker

Search messages

search_messages
Read-only

Locate Proton Mail messages by criteria including sender, recipient, subject, date, size, read/star state, and text. Returns headers newest first with paging.

Instructions

Searches a mailbox by text, subject, sender, recipient, date range, read state, star or size. At least one criterion is required. Returns headers only, newest first across pages, with paging. A full-text search walks the local database of the Bridge and takes a few seconds on a large mailbox, while criteria such as unread or date are fast. Searching "All Mail" covers every mailbox including trash.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoSubstring of a recipient address.
fromNoSubstring of the sender address or display name.
textNoFree text, matched against body and headers. This is the slow criterion.
limitNoHow many results to return.
sinceNoOnly messages on or after this date, as YYYY-MM-DD.
beforeNoOnly messages before this date, as YYYY-MM-DD.
offsetNoHow many results to skip, for paging.
mailboxNoWhich mailbox to search. Defaults to "All Mail", which holds every message.All Mail
subjectNoSubstring of the subject.
largerThanNoMinimum size in bytes. Useful for finding messages with large attachments.
unreadOnlyNoWhen true, only unread messages.
starredOnlyNoWhen true, only starred messages.
Behavior5/5

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

Discloses output format (headers only), ordering (newest first), paging, performance characteristics, and scope of 'All Mail'. This significantly extends beyond the readOnlyHint 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 concise sentences with no redundancy. Front-loaded with core function and each sentence adds essential context.

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 no output schema, description explains return shape and paging. It covers performance and mailbox scope, making the tool's behavior sufficiently clear for correct invocation.

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 already covers all parameters with descriptions (100%). Description adds context that 'text' is slow and groups criteria types, aiding understanding without duplicating schema details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it searches a mailbox by multiple criteria, using a specific verb and resource. It distinguishes from siblings through criteria and header-only return, but does not explicitly name alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States 'At least one criterion is required', implying use for filtered searches. Provides performance guidance and 'All Mail' scope, but does not explicitly contrast with list_messages or other siblings.

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

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