Skip to main content
Glama
lobster-kit

mcp-server-lobstermail

by lobster-kit

Get Thread

get_thread

Retrieve a complete email conversation thread in chronological order, showing sender, subject, and preview for each message to understand the full communication flow.

Instructions

Get a conversation thread with all its emails in chronological order. Shows the full conversation flow including sender, subject, and preview for each email.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inbox_idYesInbox ID (e.g. ibx_...)
thread_idYesThread ID (e.g. thd_...)

Implementation Reference

  • The handler function for 'get_thread' that retrieves the thread using an inbox object and formats the output.
    }, async ({ inbox_id, thread_id }) => {
      const inbox = await getInbox(inbox_id);
      const thread = await inbox.getThread(thread_id);
    
      const emailLines = thread.emails.map(
        (e, i) =>
          `${i + 1}. [${e.id}] From: ${e.from} | Subject: ${e.subject} | ${e.createdAt}` +
          (e.preview ? `\n   Preview: ${e.preview.slice(0, 100)}...` : '') +
          (e.isInjectionRisk ? '\n   ⚠️ INJECTION RISK' : ''),
      );
    
      return {
        content: [
          {
            type: 'text' as const,
            text: [
              `Thread: ${thread.subject}`,
              `Thread ID: ${thread.id}`,
              `Emails: ${thread.emailCount}`,
  • src/index.ts:322-330 (registration)
    Registration of the 'get_thread' tool with its schema and description.
    server.registerTool('get_thread', {
      title: 'Get Thread',
      description:
        'Get a conversation thread with all its emails in chronological order. ' +
        'Shows the full conversation flow including sender, subject, and preview for each email.',
      inputSchema: {
        inbox_id: z.string().describe('Inbox ID (e.g. ibx_...)'),
        thread_id: z.string().describe('Thread ID (e.g. thd_...)'),
      },
Behavior3/5

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

No annotations provided, so description carries full disclosure burden. Adds valuable behavioral context: returns items in 'chronological order' and specifies visible fields (sender, subject, preview). Missing safety classification (read-only vs. destructive), side effects (e.g., mark-as-read), and error handling for invalid IDs.

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 efficient sentences: first establishes core operation and ordering behavior, second details return payload structure. Zero redundancy—every clause adds distinct information about scope or content.

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 2-parameter retrieval tool with 100% schema coverage, description adequately compensates for missing output schema by documenting return structure (emails, fields, ordering). Minor gap: no mention of error cases (thread not found) or pagination for long threads.

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 coverage is 100% with clear parameter descriptions ('Inbox ID', 'Thread ID'). Description adds no parameter-specific guidance (e.g., where to source IDs, relationship between inbox_id and thread_id), which aligns with baseline 3 for high-coverage schemas.

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?

Excellent specificity: verb 'Get' + resource 'conversation thread', plus scope clarification ('all its emails'). Implicitly distinguishes from sibling 'get_email' (single vs. thread) and 'list_threads' (metadata list vs. full retrieval with content).

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?

Implies usage through description ('full conversation flow'), indicating use when comprehensive thread history is needed. However, lacks explicit direction on when to choose this over 'get_email' (single message) or 'list_threads' (enumeration without full content retrieval).

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/lobster-kit/mcp-server-lobstermail'

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