Skip to main content
Glama
FaisalFehad

IMAP Mail MCP

by FaisalFehad

mail_search_advanced

Search emails in IMAP mailboxes using advanced filters such as keyword, sender, receiver, subject, body, date ranges, read state, and message ID. Supports pagination and sorting.

Instructions

Primary advanced search tool: keyword, sender/receiver, subject/body, date/date-range, sent-date-range, read state, message-id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoCC contains
bccNoBCC contains
bodyNoBody contains
dateNoReceived on date (ISO, e.g. 2026-02-21)
seenNoOnly read messages
sortNoSort by UID (default: desc/newest-first)desc
limitNoMax results (default 50, capped globally)
cursorNoOpaque pagination cursor from previous response
dateToNoReceived until date/time (ISO). Date-only is inclusive.
senderNoSender contains (alias for from)
unseenNoOnly unread messages
keywordNoMatch any text in headers and body
mailboxYesFolder to search (e.g. INBOX)
subjectNoSubject contains
dateFromNoReceived since date/time (ISO)
receiverNoReceiver contains (alias for to)
sentDateNoSent on date (ISO)
messageIdNoMessage-ID header contains
returnPageNoReturn {items,nextCursor} instead of raw array
sentDateToNoSent until date/time (ISO). Date-only is inclusive.
sentDateFromNoSent since date/time (ISO)
includeSnippetNoInclude short plain-text snippet per message
Behavior2/5

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

There are no annotations, and the description does not disclose behavioral traits such as read-only nature, authentication requirements, rate limits, or side effects. The cursor parameter implies pagination, but this is not mentioned in the description.

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 a single, front-loaded sentence that immediately states the tool's primary role and key capabilities. Every word earns its place, making it highly concise and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 22 parameters, no output schema, and no annotations, the description is insufficient. It omits details on return format, pagination behavior, and usage context, which are critical for an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds high-level grouping of parameters (keyword, sender/receiver, etc.) but does not add significant meaning beyond the schema's own parameter descriptions.

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 clearly states it is an 'advanced search tool' and lists the searchable fields (keyword, sender/receiver, etc.), which conveys the purpose and distinguishes it from sibling tools like mail_list_messages or mail_search.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. The term 'primary' suggests it is the default for advanced searches, but no conditions, exclusions, or alternative tool names are provided.

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/FaisalFehad/imap-mail-mcp'

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