Fluxmail

Read email

get_email

Read-only

Read one email with recipients, body, attachment metadata, and optional headers; if the body exceeds 50,000 characters, use the truncation details to continue reading via the body tool.

Instructions

Read one email with its recipients, body and attachment metadata. The body returns at most 50,000 characters, and bodyTruncation reports where each part continues. Use get_email_body to read the rest.

Input Schema

Name	Required	Description
`accountId`	No	Account to operate on. Optional when exactly one account is connected.
`messageId`	Yes
`bodyFormat`	No
`includeHeaders`	No	Include Message-ID, References, In-Reply-To and other threading headers

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.19.0Oct 30, 2026

changedInput schema / properties / accountId / anyOf

Previous value: -[
-  {
-    "minLength": 1,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 512,
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / messageId / maxLength
```
Added value: +512
```

Changed2 schema fields changedv0.18.0Oct 28, 2026

addedInput schema / properties / includeHeaders

Added value: +{
+  "description": "Include Message-ID, References, In-Reply-To and other threading headers",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

addedOutput schema / properties / data / properties / headers

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "type": "object"
+}

Changed6 schema fields changedv0.15.0Oct 17, 2026

addedInput schema / properties / accountId / anyOf

Added value: +[
+  {
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / accountId / minLength
```
Removed value: -1
```
removedInput schema / properties / accountId / type
```
Removed value: -"string"
```

addedInput schema / properties / bodyFormat / anyOf

Added value: +[
+  {
+    "enum": [
+      "text",
+      "html",
+      "both",
+      "none"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / bodyFormat / enum

Removed value: -[
-  "text",
-  "html",
-  "both",
-  "none"
-]

removedInput schema / properties / bodyFormat / type
```
Removed value: -"string"
```

Changed1 schema field changedv0.11.1Oct 1, 2026
- removedOutput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```

Changed2 schema fields changedv0.11.0Sep 26, 2026

addedInput schema / properties / bodyFormat

Added value: +{
+  "enum": [
+    "text",
+    "html",
+    "both",
+    "none"
+  ],
+  "type": "string"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "properties": {
+        "accountId": {
+          "type": "string"
+        },
+        "attachments": {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "filename": {
+                "type": "string"
+              },
+              "id": {
+                "type": "string"
+              },
+              "mimeType": {
+                "type": "string"
+              },
+              "sizeBytes": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "id",
+              "filename",
+              "mimeType",
+              "sizeBytes"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "body": {
+          "additionalProperties": false,
+          "properties": {
+            "html": {
+              "type": "string"
+            },
+            "text": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "bodyTruncation": {
+          "additionalProperties": {
+            "additionalProperties": false,
+            "properties": {
+              "nextOffset": {
+                "type": "number"
+              },
+              "totalChars": {
+                "type": "number"
+              }
+            },
+            "required": [
+              "totalChars"
+            ],
+            "type": "object"
+          },
+          "type": "object"
+        },
+        "date": {
+          "type": "string"
+        },
+        "flags": {
+          "additionalProperties": true,
+          "properties": {
+            "draft": {
+              "type": "boolean"
+            },
+            "read": {
+              "type": "boolean"
+            },
+            "starred": {
+              "type": "boolean"
+            }
+          },
+          "required": [
+            "read",
+            "starred",
+            "draft"
+          ],
+          "type": "object"
+        },
+        "id": {
+          "type": "string"
+        },
+        "subject": {
+          "type": "string"
+        },
+        "threadId": {
+          "type": "string"
+        },
+        "to": {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "email": {
+                "type": "string"
+              },
+              "name": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "email"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "id",
+        "threadId",
+        "accountId",
+        "to",
+        "subject",
+        "date",
+        "flags"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}

First observedv0.1.0Jul 26, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare readOnly/non-destructive, and the description adds a genuine behavioral trait not visible in structured fields: bodies are capped at 50,000 characters and bodyTruncation indicates continuation points. That is exactly the kind of context that prevents an agent from assuming it got a complete message.

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 short sentences, front-loaded with what is returned, then the truncation caveat, then the escape hatch. No wasted phrasing.

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?

An output schema exists, so return values need not be spelled out, and the truncation/continuation contract is covered. The notable omission is the bodyFormat parameter's effect and any pointer to download_attachment for the referenced attachment metadata.

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

Parameters2/5

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

Schema coverage is only 50%; accountId and includeHeaders are documented in the schema, but messageId and especially bodyFormat (which controls whether text/html/both/none is returned) are described nowhere. The description mentions the body only in the context of truncation and never explains the format switch, so it fails to compensate for the coverage gap.

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?

States a specific verb and resource ('Read one email') and enumerates the payload it returns: recipients, body, attachment metadata. It is clearly distinguishable from list_emails/search_emails and it names the sibling get_email_body as the tool for the truncated remainder.

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?

Gives an explicit routing rule: when body content exceeds 50,000 characters, call get_email_body for the rest. It does not discuss when to prefer get_thread or search_emails, so the guidance is clear but not exhaustive.

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