list_emailsList recent emails sent from this account.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Page size (1–100) | |
| cursor | No | Opaque cursor for the next page |
| Name | Required | Description | Default |
|---|---|---|---|
| emails | Yes | Sent emails, newest first | |
| has_more | No | True when another page follows | |
| next_cursor | No | Pass as cursor for the next page; null on the last page |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "emails": {
+ "description": "Sent emails, newest first",
+ "items": {
+ "properties": {
+ "bcc": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "bounce_reason": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "bounced_at": {
+ "description": "ISO 8601",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "cancelled_at": {
+ "description": "ISO 8601",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "cc": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "created_at": {
+ "description": "ISO 8601",
+ "type": "string"
+ },
+ "delivered_at": {
+ "description": "ISO 8601",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "from": {
+ "type": "string"
+ },
+ "id": {
+ "description": "Email id (msg_…)",
+ "type": "string"
+ },
+ "last_event": {
+ "description": "Latest delivery event",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "reply_to": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "scheduled_at": {
+ "description": "ISO 8601",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "sent_at": {
+ "description": "ISO 8601",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "status": {
+ "type": "string"
+ },
+ "subject": {
+ "type": "string"
+ },
+ "tags": {
+ "description": "Tags set on the send"
+ },
+ "to": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "id"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "has_more": {
+ "description": "True when another page follows",
+ "type": "boolean"
+ },
+ "next_cursor": {
+ "description": "Pass as cursor for the next page; null on the last page",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "emails"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is structured data. The description adds only the scoping detail that results are limited to mail sent from this account; it says nothing about ordering, time window behind "recent", or pagination behavior beyond what the schema implies.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence with no filler and the resource front-loaded. It is efficient, though it is lean enough that there was room to add scoping detail without bloat.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a low-complexity, zero-required-parameter read tool with full schema coverage and an output schema, the description is largely sufficient — return shape and pagination are covered elsewhere. The one soft gap is that "recent" is never quantified.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and limit (page size 1–100) and cursor (opaque next-page cursor) are both documented in the schema. The description contributes no additional parameter meaning, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb+resource ("List recent emails") with a scope qualifier ("sent from this account") that implicitly separates it from siblings like list_received_emails and get_email. It does not name those siblings directly, so differentiation is inferred rather than stated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase "sent from this account" implies usage (outbound mail listing) but the description never states when to use this tool versus list_received_emails, get_email, or get_received_email. It offers implied context only, with no explicit alternatives or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.