Skip to main content
Glama
@marlinjai/email-mcp

@marlinjai/email-mcp

by marlinjai

email_get_thread

Retrieve an email thread by thread ID and account, with an optional folder lookup for IMAP/iCloud to collect related messages.

Instructions

Get an email thread by thread ID

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "accountId": "<accountId>",
      "threadId": "<threadId>"
    },
    "name": "email_get_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
threadIdYes
accountIdYes
sourceFolderNoFolder to look for the thread in on IMAP/iCloud, where a thread is searched in one folder (default INBOX). Gmail and Outlook ignore it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire behavioral burden. It does not disclose whether returned threads include all messages, in what order, whether read state changes, or what happens if the threadId is unknown; for a read tool with zero annotation coverage this is a meaningful gap.

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

Conciseness3/5

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

One short sentence with no wasted words and the key constraint (thread ID) front-loaded. Its brevity is not inefficient, but it borders on under-specification rather than crisp conciseness.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With three parameters, no annotations, and no output schema, the description should explain at least the return shape (messages within a thread) and the folder-scoping caveat. As written, an agent can invoke it but cannot predict its behavior or output.

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 33%: sourceFolder is documented in the schema, but accountId and threadId have no description and the description text adds no meaning beyond the names. The tool-specific nuance about IMAP/iCloud folder scoping exists only in the schema, not reinforced in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("Get an email thread by thread ID"), which is clearer than a tautology. However, it does not distinguish this from the sibling email_get (single message retrieval) or explain what a "thread" contains, so an agent must infer the difference from names alone.

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 guidance on when to use this versus email_get, email_search, or email_get_attachment. The only implicit cue is that a threadId is required, which mildly implies a retrieval flow, but no prerequisites or alternatives are named.

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