Sign inGet started
Menu
TOOL REFERENCE / SOURCE GENERATEDMAILMAN MCP / MAIL

email_get_thread

Returns one conversation with its messages in order, so you can read an exchange end to end instead of stitching individual messages together. Use it after email_list_threads, or with the thread_id on any message returned by a search. The account_id must be the account that owns the thread. Leave include_bodies false first if the thread is long; the snippets are usually enough to decide which message matters.

Explore the docs

Input fields

{
  "type": "object",
  "properties": {
    "account_id": {
      "type": "string",
      "minLength": 1,
      "description": "The connected mailbox to act on, from email_accounts_list. Never guess this value and never reuse one across mailboxes — it selects both the credential and the permission set the call runs under."
    },
    "thread_id": {
      "type": "string",
      "minLength": 1,
      "description": "A thread id returned by this server (thread_...), not a provider id."
    },
    "include_bodies": {
      "description": "Include every message's body. Default false. A long thread with bodies can be very large — read the snippets first.",
      "anyOf": [
        {
          "type": "boolean"
        },
        {
          "type": "null"
        }
      ]
    }
  },
  "required": [
    "account_id",
    "thread_id"
  ]
}

Tool behavior

Declared read-only. Actual provider grants and account access apply.

Inspect isError and per-account errors. General write tools do not all enforce exact-plan approval. This reference does not certify any current AI client version.

MAILMAN MCP / EMAILCapability evidence and limits ↗
YOUR AI POSTAL SYSTEM

YOUR INBOXES.
UNDER CONTROL.

Get started

Start with a free account and one read-only search. Existing accounts keep their connection.