icloud-mail

Overview Schema Source Related Servers Discussions Admin

Search Emails

search_emails

Search iCloud Mail messages by text, sender, subject, recipient, date, or folder. Filter by read status, flags, and size; results return headers from newest to oldest.

Instructions

Cherche des messages et renvoie leurs entetes, du plus recent au plus ancien.

Sans aucun critere, renvoie simplement les derniers messages du dossier. Tous les criteres se combinent en ET. La recherche, accents compris, est faite par le serveur iCloud (SEARCH CHARSET UTF-8). Si un serveur la refusait, un repli limite aux entetes des 500 messages les plus recents s'appliquerait, et le champ filtered_client_side de la reponse vaudrait alors true.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Nombre max de resultats
`query`	No	Texte libre cherche dans le message, accents acceptes
`since`	No	Date ISO minimale incluse, AAAA-MM-JJ
`before`	No	Date ISO maximale exclue, AAAA-MM-JJ
`folder`	No	Dossier a explorer	INBOX
`sender`	No	Filtre sur l'expediteur
`subject`	No	Filtre sur le sujet
`recipient`	No	Filtre sur le destinataire
`query_scope`	No	'text' cherche entetes + corps, 'body' seulement le corps	text
`unseen_only`	No	Ne garder que les non-lus
`flagged_only`	No	Ne garder que les messages marques
`larger_than_kb`	No	Taille minimale du message en kilo-octets

Output Schema

TableJSON Schema

Name	Required	Description
`folder`	Yes
`messages`	No
`returned`	Yes	Nombre de messages effectivement renvoyes
`total_matched`	Yes	Nombre de messages correspondant aux criteres
`filtered_client_side`	No	Vrai si le serveur a refuse la recherche et qu'un filtrage de repli, limite aux entetes des messages recents, a ete applique

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 21, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses server-side iCloud search, accent handling, AND combination, and a fallback behavior signaled by `filtered_client_side`. It could additionally mention auth or rate-limit traits, but the core behavioral traits are clearly covered.

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 compact, front-loaded with the main purpose, then follows with behavior and fallback details. Every sentence contributes useful information without redundancy.

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?

For a 12-parameter tool with no annotations, the description covers default behavior, search semantics, and the fallback path well. The main gap is not clarifying the single-folder scope versus search_all_folders, but the output schema and parameter descriptions handle the remaining details.

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 the baseline is 3. The description adds meaningful cross-parameter semantics beyond the schema, such as criteria being combined with AND and the fallback affecting the response field `filtered_client_side`, which helps an agent reason about parameter interactions.

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?

The description states a specific action ('Cherche des messages') and resource ('renvoie leurs entetes'), with clear ordering from newest to oldest. It does not explicitly differentiate itself from the sibling tool search_all_folders, so it misses the top score.

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

Usage Guidelines3/5

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

The description provides useful invocation context: empty criteria return latest messages, and all criteria combine with AND. However, it gives no explicit guidance on when to prefer this tool over search_all_folders or other siblings.

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

Deploy Server