Skip to main content
Glama
Wh1isper

MCP Email Server

by Wh1isper
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

list_emails_metadata

Read-onlyIdempotent

Fetch email metadata—subject, sender, recipients, date—without loading bodies. Filter by mailbox, sender, subject, read status, and more, then use returned email IDs to retrieve full content.

Instructions

List email metadata (email_id, subject, sender, recipients, date) without body content. Time filtering and ordering use provider INTERNALDATE; the returned date is the message's RFC 5322 Date header. Returns email_id for use with get_emails_content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoSearch for text in the email body (IMAP BODY).
pageNoThe page number to retrieve (starting from 1).
seenNoFilter by read status: True=read, False=unread, None=all.
textNoSearch for text in the entire message — headers and body (IMAP TEXT).
orderNoSort matching emails by provider INTERNALDATE: oldest first (`asc`) or newest first (`desc`).desc
sinceNoFilter to messages whose provider INTERNALDATE is equal to or later than this timezone-aware datetime (inclusive); any UTC offset is accepted and normalized to UTC.
beforeNoFilter to messages whose provider INTERNALDATE is earlier than this timezone-aware datetime (exclusive); any UTC offset is accepted and normalized to UTC.
flaggedNoFilter by flagged/starred status: True=flagged, False=unflagged, None=all.
mailboxNoThe mailbox to search.INBOX
subjectNoFilter emails by subject.
answeredNoFilter by replied status: True=replied, False=not replied, None=all.
page_sizeNoThe number of emails to retrieve per page.
tag_matchNoRequire all requested tags or at least any one requested tag.all
to_addressNoFilter emails by recipient address.
account_nameYesThe name of the email account.
from_addressNoFilter emails by sender address.
semantic_tagsNoConfigured semantic tag names to match.
has_attachmentNoFilter by attachment presence: True=has attachment, False=none, None=all (multipart/mixed heuristic; may miss inline images or yield false positives).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYes
sinceYes
totalYes
beforeYes
emailsYes
subjectYes
warningsNo
page_sizeYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed7 schema fields changedv1.6.2
    • changedInput schema / properties / before / description
      Previous value: -"Retrieve emails before this datetime (UTC)."New value: +"Filter to messages whose provider INTERNALDATE is earlier than this timezone-aware datetime (exclusive); any UTC offset is accepted and normalized to UTC."
    • changedInput schema / properties / order / description
      Previous value: -"Sort matching emails by date: oldest first (`asc`) or newest first (`desc`)."New value: +"Sort matching emails by provider INTERNALDATE: oldest first (`asc`) or newest first (`desc`)."
    • addedInput schema / properties / semantic_tags
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "maxLength": 128,
+        "type": "string"
+      },
+      "maxItems": 100,
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Configured semantic tag names to match.",
+  "title": "Semantic Tags"
+}
    • changedInput schema / properties / since / description
      Previous value: -"Retrieve emails since this datetime (UTC)."New value: +"Filter to messages whose provider INTERNALDATE is equal to or later than this timezone-aware datetime (inclusive); any UTC offset is accepted and normalized to UTC."
    • addedInput schema / properties / tag_match
      Added value: +{
+  "default": "all",
+  "description": "Require all requested tags or at least any one requested tag.",
+  "enum": [
+    "all",
+    "any"
+  ],
+  "title": "Tag Match",
+  "type": "string"
+}
    • addedOutput schema / $defs / EmailMetadata / properties / provider_keywords
      Added value: +{
+  "items": {
+    "maxLength": 128,
+    "type": "string"
+  },
+  "maxItems": 100,
+  "title": "Provider Keywords",
+  "type": "array"
+}
    • addedOutput schema / $defs / EmailMetadata / properties / semantic_tags
      Added value: +{
+  "items": {
+    "maxLength": 128,
+    "type": "string"
+  },
+  "maxItems": 100,
+  "title": "Semantic Tags",
+  "type": "array"
+}
  2. Addedv1.1.1
  3. Removedv1.0.1
  4. Changed3 schema fields changedv0.13.0
    • addedInput schema / properties / body
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Search for text in the email body (IMAP BODY).",
+  "title": "Body"
+}
    • addedInput schema / properties / has_attachment
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Filter by attachment presence: True=has attachment, False=none, None=all (multipart/mixed heuristic; may miss inline images or yield false positives).",
+  "title": "Has Attachment"
+}
    • addedInput schema / properties / text
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Search for text in the entire message — headers and body (IMAP TEXT).",
+  "title": "Text"
+}
  5. Addedv0.8.0
  6. Removedv0.7.0
  7. Changed4 schema fields changedv0.6.3
    • addedInput schema / properties / answered
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Filter by replied status: True=replied, False=not replied, None=all.",
+  "title": "Answered"
+}
    • addedInput schema / properties / flagged
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Filter by flagged/starred status: True=flagged, False=unflagged, None=all.",
+  "title": "Flagged"
+}
    • changedInput schema / properties / mailbox / description
      Previous value: -"The mailbox to retrieve emails from."New value: +"The mailbox to search."
    • addedInput schema / properties / seen
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Filter by read status: True=read, False=unread, None=all.",
+  "title": "Seen"
+}
  8. Addedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent/non-destructive annotations, the description discloses a subtle and important behavioral distinction: time filtering and ordering use provider INTERNALDATE, while the returned date is the RFC 5322 Date header. It also clearly states the tool omits body content, which is behaviorally important for agents deciding whether to call get_emails_content.

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?

Three tight sentences, each earning its place: what the tool returns, the key date semantics caveat, and the integration path to get_emails_content. There is no redundant restatement of the schema or annotations.

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

Completeness5/5

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

For a tool with 18 parameters, annotations fully cover safety, an output schema exists, and all parameters are documented in the schema, the description supplies the missing qualitative context: metadata-only scope, date semantics, and the link to a sibling tool. No critical gap remains for an agent to invoke this correctly.

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 coverage is 100%, so the baseline is 3. The description adds value beyond the schema by clarifying the relationship between INTERNALDATE-based filtering/ordering and the RFC 5322 Date header returned in results. This helps an agent understand why date filters may not match the displayed date.

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 uses a specific verb and resource: 'List email metadata' and enumerates the exact fields returned (email_id, subject, sender, recipients, date). It also explicitly states what it does NOT return ('without body content'), immediately distinguishing it from content-fetching siblings like get_emails_content.

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 gives clear workflow context by noting 'Returns email_id for use with get_emails_content', which implies a metadata-first workflow. However, it does not explicitly state when not to use this tool or name alternatives, so it stops short of fully explicit routing guidance.

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

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