Skip to main content
Glama
Sign In
your-mail-mcp

your-mail-mcp

by wildsurfer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

thread

Read-only

Retrieves the complete email conversation containing a message by ID; junk and trash replies are omitted unless explicitly included.

Instructions

Show the whole thread containing a message. Excludes junk/trash replies by default; set include_excluded to include them.

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": {
      "id": "<id>"
    },
    "name": "thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMessage-ID of the message, as search, ids and show report it, with or without the surrounding angle brackets.
limitNoHow many bytes of text to return at most. Defaults to 65536, which is also the ceiling.
offsetNoByte offset to resume the text from. Use the offset named in a [truncated] marker to read the next chunk of a long message. Defaults to 0, the start.
include_excludedNoSet true to read a message that lives in junk or trash, which are left out by default. Use it only when the message is expected to be there, since mail in those folders is more likely to be hostile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.5.0
    • addedInput schema / properties / id / description
      Added value: +"Message-ID of the message, as search, ids and show report it, with or without the surrounding angle brackets."
    • addedInput schema / properties / include_excluded / description
      Added value: +"Set true to read a message that lives in junk or trash, which are left out by default. Use it only when the message is expected to be there, since mail in those folders is more likely to be hostile."
    • addedInput schema / properties / limit / description
      Added value: +"How many bytes of text to return at most. Defaults to 65536, which is also the ceiling."
    • addedInput schema / properties / offset / description
      Added value: +"Byte offset to resume the text from. Use the offset named in a [truncated] marker to read the next chunk of a long message. Defaults to 0, the start."
  2. First observedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, closed-world behavior, so the bar is lower. The description usefully adds that junk/trash replies are excluded by default and that include_excluded changes this, which is meaningful behavioral context beyond the annotations.

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 concise sentences, front-loaded with the primary action and followed by the key default-filtering behavior. Every sentence earns its place.

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?

For a simple read-only thread retrieval tool with fully documented parameters and safety annotations, the description is largely complete. A minor gap is that it does not mention pagination or the shape of the returned thread, though the input schema covers limit/offset.

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 100%, so the schema already documents all four parameters in detail. The description repeats the include_excluded default behavior but adds no syntax, format, or usage detail beyond the schema.

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: 'Show the whole thread containing a message.' It is clearly distinguishable from sibling tools like 'show' or 'search' by scope, though it does not explicitly name alternatives.

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?

It implies the use case of retrieving a full thread from a message ID, and explains the default filtering behavior. However, it does not explicitly say when to use this tool versus 'show', 'search', or 'text', nor does it state exclusions or alternatives.

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