Skip to main content
Glama
eduardobrito21

fastmail-mcp

query_emails

Filter your Fastmail inbox by sender, subject, date, keywords, or attachments to retrieve matching emails with previews.

Instructions

Search for emails with structured filters. Returns matching emails with preview.

Args: in_mailbox: Mailbox ID to search within. text: Full-text search across all fields (from, to, subject, body). from_addr: Filter by sender address or name. to_addr: Filter by recipient address or name. subject: Filter by subject text. after: Emails received after this date (ISO 8601, e.g. "2024-01-01T00:00:00Z"). before: Emails received before this date (ISO 8601). has_keyword: Require keyword/flag ("$flagged", "$seen", "$draft", "$answered"). not_keyword: Exclude emails with this keyword. has_attachment: Filter by attachment presence. filter_json: Raw JSON FilterCondition for complex queries (overrides other filter params). sort_property: Sort field — receivedAt, sentAt, from, to, subject, size. sort_ascending: Sort direction (default: newest first). limit: Max results (1–100, default 20).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
in_mailboxNo
textNo
from_addrNo
to_addrNo
subjectNo
afterNo
beforeNo
has_keywordNo
not_keywordNo
has_attachmentNo
filter_jsonNo
sort_propertyNoreceivedAt
sort_ascendingNo
limitNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

With no annotations provided, the description must disclose behavioral traits. It indicates a read operation ('Search... Returns') but does not explicitly state non-destructive nature, authentication needs, rate limits, or pagination behavior. The description is adequate but lacks explicit safety or constraint details beyond the return preview.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a brief opening sentence followed by an Args list. It is concise but slightly lengthy due to the number of parameters. Every sentence adds value, and the main purpose is front-loaded.

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 search tool with 14 optional parameters and an output schema, the description adequately covers the filtering capabilities, including the filter_json override. It explains limits, sorting, and date formats. However, it omits details on what the 'preview' return contains, though the output schema likely covers that. Overall complete.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate fully. It provides clear, per-parameter explanations in the Args section, adding meaning beyond the raw schema (which lacks descriptions). Each parameter's purpose, format (e.g., ISO 8601 for dates), and defaults are explained.

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 states 'Search for emails with structured filters. Returns matching emails with preview.' This effectively communicates a specific verb (search) and resource (emails), and distinguishes it from sibling tools like get_emails or get_recent_emails by emphasizing structured filtering.

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 implies usage for filtered email search via parameter details, but it does not explicitly state when to use this tool versus alternatives such as get_emails, bulk operations, or get_recent_emails. No exclusion criteria or contextual guidance is 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/eduardobrito21/fastmail-mcp'

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