Skip to main content
Glama
sweetrb

apple-mail-mcp

by sweetrb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get-thread

Retrieve all messages in a conversation thread given one message ID, ordered oldest-first. Threads by References/Message-ID or normalized subject.

Instructions

Use when: you have one message id and want the whole conversation it belongs to, oldest-first. With an imap: id it threads by References/Message-ID; otherwise it groups by normalized subject. Returns: the thread's normalized subject and its messages (id, date, subject, sender, read state). Do not use when: you only need the single message (use get-message) or are searching by arbitrary criteria (use search-messages).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesA message ID in the conversation (numeric or imap:…)
limitNoMax messages in the thread (default 50)
accountNoAccount to search (omit to search all)
mailboxNoMailbox to search (omit to search all)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
partialNo
subjectNo
messagesNo
failedMailboxesNo
omittedMessagesNo
failedMailboxReasonsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.19.19
    • addedOutput schema / properties / failedMailboxReasons
      Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / omittedMessages
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "string"
+      },
+      "mailbox": {
+        "type": "string"
+      },
+      "reason": {
+        "type": "string"
+      },
+      "uid": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "id",
+      "mailbox",
+      "uid",
+      "reason"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  2. Changed1 schema field changedv2.17.2
    • addedOutput schema / properties / failedMailboxes
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  3. Changed2 schema fields changedv2.10.24
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. Changed1 schema field changedv2.10.8
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
  5. Addedv2.8.14
  6. Removedv2.8.10
  7. First observedv2.6.1

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key non-obvious behavior: imap: ids thread via References/Message-ID while other ids fall back to normalized-subject grouping, plus what the response contains. It does not cover permissions, throttling, or how the limit interacts with very large threads, but the threading semantics are the material trait here.

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 labeled, front-loaded sentences (when / returns / do-not-use-when) with no filler. Every clause carries decision-relevant information for the agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 enumerated, yet the description still gives a compact summary of the payload. Combined with threading semantics and explicit routing to siblings, nothing an agent needs to invoke this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3 and the schema already documents all four parameters. The description adds genuine meaning beyond that by explaining that the id format changes the threading algorithm, which is not derivable from the pattern regex alone.

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 (retrieve the whole conversation) on a specific resource (a thread keyed off one message id), including the ordering (oldest-first). It explicitly distinguishes itself from get-message and search-messages by name, so an agent can route without reading any schema.

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

Usage Guidelines5/5

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

Uses an explicit when / do-not-use-when structure: use it when you have one message id and want its conversation; do not use it for a single message (get-message) or arbitrary-criteria search (search-messages). Both alternatives are named with the condition that selects them.

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

Deploy Server

Other Tools