Skip to main content
Glama
chandshy

mailpouch

by chandshy
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Get Email Thread

get_thread
Read-only

Retrieves all messages sharing a normalized subject with a given email, collecting related replies from INBOX and Sent. Use this to summarize an entire conversation in one call.

Instructions

Return all messages that look like they belong to the same thread as the given email. Uses the normalized Subject (Re:/Fwd: stripped) to collect related messages from INBOX + Sent. Folder-restricted agents only receive messages from their allowed folders. Useful for summarising long conversations in one call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderNoFolder the seed message lives in. Providing this avoids UID collisions across folders.
email_idYesIMAP UID of any message in the thread
account_idNoOptional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).
max_messagesNoMax messages to return (default 50, cap 200)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
subjectYesNormalized subject line for the thread
messagesYesMessages in the thread, oldest-first

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv3.1.0
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Optional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).",
+  "type": "string"
+}
  2. First observedv3.0.77

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true. The description adds behavioral details: normalized Subject stripping, collection from INBOX+Sent, and folder restrictions for restricted agents. This adds valuable context beyond 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?

Three sentences, front-loaded with purpose, then method, then use case. Every sentence provides value with no redundancy.

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?

Covers purpose, method, and restrictions. With an output schema present, return values need not be explained. Lacks discussion of edge cases like thread size limits or ordering, but sufficient for typical use.

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?

All four parameters have schema descriptions (100% coverage), so the description adds little extra parameter meaning. It mentions folder restrictions but does not elaborate on parameter details beyond the schema.

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?

The description explicitly states it returns all messages belonging to the same thread, using normalized Subject to collect from INBOX+Sent. This clearly distinguishes it from sibling tools like search_emails or get_emails.

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

Usage Guidelines4/5

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

The description indicates it's useful for summarizing long conversations, providing clear context for when to use it. However, it does not explicitly state when not to use it or compare to alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chandshy/mailpouch'

If you have feedback or need assistance with the MCP directory API, please join our Discord server