Skip to main content
Glama

search-emails

Read-only

Search and list emails using queries, KQL, or filters like sender, subject, folder, and date. Also supports delta sync and conversation threading.

Instructions

Search and list emails. With no query, lists recent emails (like list-emails). Supports search queries, KQL, delta sync, message-id lookup, and conversation listing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deltaModeNoEnable delta sync mode. Returns only changes since last sync. Use deltaToken for subsequent calls.
internetMessageIdNoLook up email by Message-ID header (e.g. <abc123@example.com>). For threading/deduplication.
conversationIdNoGet all messages in a conversation thread by conversationId.
groupByConversationNoList conversations (threads) grouped by conversationId instead of individual emails.
queryNoSearch query text. Omit for list mode.
kqlQueryNoRaw KQL (Keyword Query Language) query for advanced search. Bypasses other search params.
folderNoEmail folder (default: 'inbox')
fromNoFilter by sender email/name
toNoFilter by recipient email/name
subjectNoFilter by subject
hasAttachmentsNoFilter to emails with attachments
unreadOnlyNoFilter to unread emails only
receivedAfterNoFilter emails received after date (ISO 8601)
receivedBeforeNoFilter emails received before date (ISO 8601)
searchAllFoldersNoSearch across all mail folders
countNoNumber of results (list default: 25, search default: 10, max: 50)
outputVerbosityNoOutput detail level (default: standard)
deltaTokenNoToken from previous delta call for incremental sync (deltaMode only)
maxResultsNoMax results per page for delta sync (default: 100, max: 200)
includeHeadersNoInclude email headers for each message (conversationId only)
Behavior4/5

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

The description discloses multiple search modes and behaviors (delta sync, conversation listing, etc.), adding valuable context beyond the readOnlyHint annotation. It does not contradict annotations and offers good transparency into the tool's capabilities.

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 extremely concise: three short sentences that immediately convey the core purpose, default behavior, and supported modes. Every sentence adds value with no redundancy.

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

Completeness3/5

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

Given the complexity (20 parameters, no output schema), the description covers the main function modes but omits details on output behavior, pagination, or default result handling. It is adequate but leaves gaps for an agent to infer.

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?

All 20 parameters have descriptions in the input schema, achieving 100% coverage. The tool description does not provide any additional parameter-level meaning beyond what the schema already states, meeting the baseline expectation.

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 that the tool searches and lists emails, and enumerates specific capabilities (KQL, delta sync, etc.). It implies a similarity to list-emails but does not explicitly differentiate from sibling tools, though the purpose is still clear.

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?

The description provides no explicit guidance on when to use this tool versus its siblings (e.g., read-email). It only notes that without a query it acts like list-emails, but that tool is not listed among siblings, leaving the agent without clear usage boundaries.

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/littlebearapps/outlook-mcp'

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