Skip to main content
Glama

search-emails

Read-only

Search for emails using simple text, KQL queries, or message ID. List recent emails, sync changes with delta mode, or view conversation threads.

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?

Annotations declare readOnlyHint=true, and the description adds behavioral context about various modes (delta, KQL, conversation). It does not describe output format or auth needs, but the safety profile is clear and the modes add useful transparency.

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?

Two sentences with no unnecessary words. The first sentence states the core purpose, and the second lists capabilities. Efficient and front-loaded.

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?

With 20 parameters and no output schema, the description covers the main modes but lacks guidance on parameter interactions or mode selection (e.g., when to use query vs. kqlQuery). Some context is left to the schema, but overall it's adequate for a tech-savvy agent.

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 description coverage is 100%, so baseline is 3. The description adds value by grouping parameters into modes (e.g., search queries, KQL, delta sync) and explaining their purpose, which enhances understanding beyond individual param descriptions.

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

Purpose5/5

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

The description clearly specifies the action 'search and list emails' and covers multiple modes like search, list, delta sync, message-id lookup, and conversation listing, distinguishing it from siblings like read-email or send-email.

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?

The description provides context on when to use the tool, e.g., 'With no query, lists recent emails' and lists supported operations. However, it does not explicitly state when not to use it or provide direct comparisons to alternatives.

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-assistant'

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