Fluxmail Cloud

Read email

get_email

Read-only

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.

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.

Changed1 schema field changedOct 31, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "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"
+        },
+        "headers": {
+          "additionalProperties": {
+            "type": "string"
+          },
+          "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"
+}

Changed2 schema fields changedOct 29, 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
```

Changed12 schema fields changedOct 27, 2026

changedInput schema / $schema

Previous value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / properties / accountId / anyOf

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

addedInput schema / properties / accountId / description

Added value: +"Account to operate on. Optional when exactly one account is connected."

removedInput schema / properties / accountId / maxLength
```
Removed value: -512
```
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"
```

addedInput schema / properties / includeHeaders / description

Added value: +"Include Message-ID, References, In-Reply-To and other threading headers"

changedInput schema / properties / includeHeaders / type

Previous value: -"boolean"New value: +[
+  "boolean",
+  "null"
+]

removedInput schema / properties / messageId / maxLength
```
Removed value: -512
```

Changed1 schema field changedOct 25, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed1 schema field changedOct 23, 2026

addedInput schema / properties / bodyFormat

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

First observedOct 15, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds genuinely non-obvious behavior: bodies are capped at 50,000 characters and truncation is surfaced via a bodyTruncation field so the caller knows where parts continue. It stops short of describing error behavior for an invalid messageId or the default bodyFormat.

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 tightly written sentences with zero filler; the truncation caveat is placed immediately after the claim it qualifies, and the payload enumeration is front-loaded.

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 an output schema present the description needn't explain return values, and annotations carry the safety semantics, so what remains — payload scope plus truncation behavior — is covered. The one meaningful gap is sibling disambiguation against get_email_body and get_thread.

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 description coverage is only 50%: accountId and includeHeaders are documented, but messageId and the bodyFormat enum (text/html/both/none) are bare in the schema. The description hints at body behavior and truncation but never explains what bodyFormat values do or that 'none' skips the body entirely, so it does not compensate for the coverage gap.

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 ('Read one email') and enumerates the payload (recipients, body, attachment metadata), so its scope is clear. It does not, however, differentiate itself from close siblings like get_email_body or get_thread, leaving the agent to infer why reading the whole message beats reading only the body.

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?

Usage is only implied: the agent can infer this is the tool for fetching a single message once it has a messageId. There is no explicit when-to-use statement, no precondition about needing a messageId from list_emails/search_emails first, and no pointer to get_email_body for body-only reads or download_attachment for the attachments.

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

All Fluxmail Cloud tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?