Skip to main content
Glama

search_emails

Read-only

Search a Proton Mail mailbox by sender, recipient, subject, text, date range, folder, or unread status; returns newest matching email headers first.

Instructions

Search emails in a folder, newest first (headers only).

from_/to/subject/text are case-insensitive substring matches (text searches headers and body). since/before are ISO dates (YYYY-MM-DD); before is exclusive. The default folder 'All Mail' covers the whole mailbox.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
textNo
from_No
limitNo
sinceNo
beforeNo
folderNoAll Mail
subjectNo
unread_onlyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish this is a safe, non-open-world read, so the description's job is to add operational detail — and it does: results are newest first, only headers come back even though text matches against the body, before is exclusive, and the default folder is mailbox-wide. What is missing is behavior for limit overflow or empty result sets, which keeps it from a 5.

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 short blocks, front-loaded with the core action and ordering, then match semantics, then date and folder rules. Every sentence conveys a rule an agent could not infer from the schema, and nothing is repeated from the structured fields.

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?

An output schema exists, so return values need no explanation, and the description correctly limits itself to input semantics plus the 'headers only' caveat. It is nearly complete for a nine-parameter search tool, lacking only guidance on limit and unread_only.

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 0% schema description coverage the description carries the whole burden, and it defines match semantics (case-insensitive substring) for from_/to/subject, notes that text spans headers and body, gives the date format and exclusivity rule for since/before, and explains the folder default. Two of the nine parameters, limit and unread_only, receive no explanation at all, which is the only real gap.

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 opening sentence names a specific verb and resource ("Search emails in a folder") and adds two distinguishing traits: result ordering (newest first) and return scope (headers only), which implicitly separates it from read_email. It stops short of explicitly contrasting itself with list_emails, so it falls just below the top mark.

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?

Usage is implied rather than stated: the presence of from_/to/subject/text filters signals this is the filtered-lookup tool, and the note that the default 'All Mail' folder spans the whole mailbox hints at scope selection. There is no explicit "use this when... / use list_emails when..." routing, and no mention of what to do when no filters are supplied.

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