Skip to main content
Glama
ai-zerolab

MCP Email Server

by ai-zerolab

list_emails_metadata

Retrieve email metadata including ID, subject, sender, recipients, and date without body content. Filter by mailbox, date range, subject, sender, recipient, read/flagged/answered status, and paginate results.

Instructions

List email metadata (email_id, subject, sender, recipients, date) without body content. Returns email_id for use with get_emails_content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_nameYesThe name of the email account.
pageNoThe page number to retrieve (starting from 1).
page_sizeNoThe number of emails to retrieve per page.
beforeNoRetrieve emails before this datetime (UTC).
sinceNoRetrieve emails since this datetime (UTC).
subjectNoFilter emails by subject.
from_addressNoFilter emails by sender address.
to_addressNoFilter emails by recipient address.
orderNoOrder emails by field. `asc` or `desc`.desc
mailboxNoThe mailbox to search.INBOX
seenNoFilter by read status: True=read, False=unread, None=all.
flaggedNoFilter by flagged/starred status: True=flagged, False=unflagged, None=all.
answeredNoFilter by replied status: True=replied, False=not replied, None=all.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
page_sizeYes
beforeYes
sinceYes
subjectYes
emailsYes
totalYes
Behavior2/5

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

With no annotations, the description carries full burden. It only states what is returned (metadata without body) but does not disclose pagination behavior, read-only nature, authentication requirements, or any side effects. For a tool with 13 parameters, this is insufficient behavioral detail.

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 contain all necessary purpose and linkage information without any wasted words. The description is front-loaded with the primary action and key output.

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?

Given the high parameter count and existence of output schema, the description covers the core purpose and links to get_emails_content. While it omits summary of filtering capabilities, the schema fully documents parameters. The description is adequate for the task.

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 baseline is 3. The tool description does not add any parameter-specific meaning beyond what is already in the schema. It only provides context on the purpose, not on parameter usage.

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?

Description clearly states the tool lists email metadata, specifies fields (email_id, subject, sender, recipients, date), and explicitly distinguishes from get_emails_content by noting it returns email_id for that tool. This provides specific verb+resource and differentiates from a sibling tool.

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 browsing metadata and then using get_emails_content for body, but it does not explicitly state when to use or not use this tool vs alternatives. No guidance on filters or pagination is provided, leaving the agent to infer context from the schema.

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/ai-zerolab/mcp-email-server'

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