Groundmail

List emails

list_emails

Read-onlyIdempotent

List recent emails sent from this account. Test emails (test keys, simulator addresses) have test: true.

Input Schema

Name	Required	Description
`test`	No	true: only test emails; false: only live ones. Omit for both
`limit`	No	Page size (1–100)
`cursor`	No	Opaque cursor for the next page
`stream`	No	Only emails sent on this mail stream
`tenant`	No	Only emails sent as this tenant. The tenant's external id (your id for that customer) or its Groundmail id

Output Schema

Name	Required	Description
`emails`	Yes	Emails on this page, newest first
`has_more`	No	True when another page of results is available
`next_cursor`	No	Cursor to pass as `cursor` to fetch the next page; null on the last page

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

changedOutput schema / properties / emails / items / properties / held_back / items / properties / reason / description

Previous value: -"Why: invalid_address (cannot exist), no_mail_server (domain takes no email), previously_bounced (hard-bounced for a Groundmail sender in the last 90 days) or mailbox_not_found"New value: +"Why: invalid_address (cannot exist), no_mail_server (domain takes no email), previously_bounced (hard-bounced for a Groundmail sender in the last 90 days), mailbox_not_found, or likely_bot_signup (looks like a bot sign-up; only when the send opted in)"

Changed1 schema field changedNov 3, 2026

addedOutput schema / properties / emails / items / properties / batch_id

Added value: +{
+  "description": "The batch send it came from (batch_…), for get_batch and cancel_batch; null for a single send",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedOct 30, 2026

addedOutput schema / properties / emails / items / properties / delivery

Added value: +{
+  "description": "What the recipient's mail server said about the latest delivery attempt. Null until an attempt reports one, and for test emails. delivered_at minus created_at is how long it took to land",
+  "properties": {
+    "deferred_at": {
+      "description": "When the latest deferral happened (ISO 8601)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "deferred_response": {
+      "description": "Its reply to the latest deferral (a 4xx such as greylisting; delivery is retried); null when none",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "receiving_server": {
+      "description": "Hostname of the recipient's mail server, e.g. gmail-smtp-in.l.google.com",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "response": {
+      "description": "Its exact SMTP reply to the latest attempt that finished: 250 … when it accepted the email, 5xx … when it refused it",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "tls": {
+      "description": "Whether the connection used TLS; null when the attempt did not say",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "receiving_server",
+    "response",
+    "tls",
+    "deferred_response",
+    "deferred_at"
+  ],
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed2 schema fields changedOct 19, 2026

addedInput schema / properties / stream

Added value: +{
+  "description": "Only emails sent on this mail stream",
+  "enum": [
+    "transactional",
+    "product",
+    "newsletter"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / emails / items / properties / stream

Added value: +{
+  "description": "Mail stream it went out on: transactional, product or newsletter (each sends from its own IPs)",
+  "type": "string"
+}

Changed2 schema fields changedOct 18, 2026

addedInput schema / properties / tenant

Added value: +{
+  "description": "Only emails sent as this tenant. The tenant's external id (your id for that customer) or its Groundmail id",
+  "type": "string"
+}

addedOutput schema / properties / emails / items / properties / tenant

Added value: +{
+  "description": "External id of the tenant the email was sent as. Present only when it was sent as a tenant",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed2 schema fields changedOct 18, 2026

addedInput schema / properties / test

Added value: +{
+  "description": "true: only test emails; false: only live ones. Omit for both",
+  "type": "boolean"
+}

addedOutput schema / properties / emails / items / properties / test

Added value: +{
+  "description": "True when the email never reached the mail server: sent with a test key (gm_test_…) or only to simulator addresses. Its status and events are simulated",
+  "type": "boolean"
+}

Changed1 schema field changedOct 18, 2026

addedOutput schema / properties / emails / items / properties / held_back

Added value: +{
+  "description": "Recipients Groundmail validation held back before sending, with why; empty when none were",
+  "items": {
+    "properties": {
+      "email": {
+        "description": "The held-back address",
+        "type": "string"
+      },
+      "reason": {
+        "description": "Why: invalid_address (cannot exist), no_mail_server (domain takes no email), previously_bounced (hard-bounced for a Groundmail sender in the last 90 days) or mailbox_not_found",
+        "type": "string"
+      }
+    },
+    "required": [
+      "email",
+      "reason"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedOct 17, 2026

addedOutput schema / properties / emails / items / properties / bounce_type

Added value: +{
+  "description": "Why it bounced: hard (address cannot receive; suppressed) or block (the receiving server refused the sender for reputation or policy; address not suppressed, safe to retry later). Null if it did not bounce",
+  "enum": [
+    "hard",
+    "block",
+    null
+  ],
+  "type": [
+    "string",
+    "null"
+  ]
+}

First observedOct 16, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds one useful piece of context — that test sends are tagged test: true — but says nothing about pagination behavior despite cursor/limit parameters, or ordering/'recent' window.

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 short sentences, scope first then the test-email caveat. No filler and nothing buried.

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?

With a full output schema and comprehensive annotations, the description only needs to frame scope, which it does. It falls slightly short by not clarifying how this differs from the sibling test-email listing or what 'recent' means, but an agent can call it correctly from what is present.

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% and each parameter already carries its own documentation, so baseline is 3. The description only reinforces the test flag semantics and adds nothing about limit ranges, cursor mechanics, or stream/tenant filtering beyond what the schema says.

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?

States a specific verb and resource ('List recent emails sent from this account'), which usefully distinguishes it from list_received_emails by direction. However it does not address the overlap with list_test_emails or list_emails' relationship to get_email, so sibling differentiation is only partial.

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?

Implicit guidance only: 'recent emails sent from this account' tells the agent this is the outbound listing, but there is no explicit when-to-use versus list_test_emails, which sits adjacent and covers the test case the description itself raises. No exclusions or prerequisites stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Groundmail tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?