Fluxmail Cloud

Read draft

get_draft

Read-only

Read an existing draft by its draft ID.

Input Schema

Name	Required	Description	Default
`draftId`	Yes
`accountId`	No	Account to operate on. Optional when exactly one account is connected.

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"
+        },
+        "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 / draftId / maxLength
```
Added value: +512
```

Changed7 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"
```
removedInput schema / properties / draftId / 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"

First observedOct 15, 2026

TDQS

B3.2/5.0

Behavior3/5

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 fully covered and the description does not contradict it. The description adds essentially no behavioral detail beyond the annotations – no mention of what happens for an unknown draftId or whether a missing draft errors versus returns empty – so it neither helps nor harms.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero wasted words. It is appropriately sized for a simple single-resource read, though it is so terse that it leaves useful context on the table.

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 explained, and annotations cover the safety profile. For a two-parameter read tool, the remaining gaps – unknown-ID behavior and when to pass accountId – are minor, making the definition adequate for correct invocation.

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 50%: accountId is documented in the schema, while draftId has no schema description. The description supplies the missing meaning for draftId ('by its draft ID'), which is the minimum needed to call the tool, but it adds nothing about format, length bounds, or the optional accountId fallback behavior.

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 an existing draft') plus the key identifier ('by its draft ID'), which cleanly separates it from create_draft, update_draft, and delete_draft. It does not, however, differentiate itself from other read tools like get_email or get_thread beyond the resource name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no mention of prerequisites, and no named alternatives (e.g. use list_emails or get_email for non-drafts). The agent must infer usage purely from the tool name and the word 'draft'.

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?