Skip to main content
Glama
Sign In
Email Sending MCP

Email Sending MCP

by resend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Inbox Thread Email

get-inbox-thread-email
Read-only

Read one inbox thread message in full: html and text body, addresses, Message-ID, and attachment list. Use it after listing a thread to fetch a single message body.

Instructions

Purpose: Read one message in a Resend inbox thread, body included: its html and text, its addresses and Message-ID, and the attachments it carries.

NOT for: Reading a whole conversation at once (use get-inbox-thread, which lists a thread's messages without their bodies). Not for emails sent with send-email (use get-email), and not for mail at the account's Resend receiving address (use get-received-email).

Returns: The message's email ID, direction (inbound or outbound), from, to, cc, bcc, reply_to, subject, message_id, read state, received_at, one line per attachment (filename, size and attachment ID), and the html and text bodies it has.

When to use: get-inbox-thread points here for a body. Take the "Email ID" it printed for the message the user wants and pass it as emailId. Attachment contents cannot be downloaded through this server: attachments are listed, not fetched.

Input Schema

NameRequiredDescriptionDefault
emailIdYesID of the message to read. This is the "id" get-inbox-thread returns for each message in the thread.
inboxIdYesInbox ID, or the inbox email address (e.g. "support@example.com"). Not the Resend receiving address.
threadIdYesThread ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.27.1
    • changedInput schema / properties / inboxId / description
      Previous value: -"Inbox ID"New value: +"Inbox ID, or the inbox email address (e.g. \"support@example.com\"). Not the Resend receiving address."
  2. Addedv2.26.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description still adds genuine behavioral context beyond them: attachments are listed but never fetched, and attachment contents cannot be downloaded through this server. It does not discuss pagination or error behavior, but the listed constraints are the ones an agent would otherwise get wrong.

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

Conciseness4/5

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

Labeled sections (Purpose / NOT for / Returns / When to use) front-load the purpose and keep routing information scannable. It is somewhat long, and the Returns inventory partly restates field names that the schema already implies, but with no output schema that enumeration is not wasted.

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?

No output schema exists, so the explicit Returns enumeration (id, direction, from/to/cc/bcc, reply_to, subject, message_id, read state, received_at, attachment lines, html/text) is necessary and supplied. Combined with the routing guidance and the attachment limitation, an agent has everything needed to call this correctly.

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 description coverage is 100%, so the baseline is 3. The description goes further by explaining the cross-tool provenance of emailId (take the 'Email ID' printed by get-inbox-thread) and reinforcing that inboxId is not the Resend receiving address. Minor inconsistency: the schema says the value is the 'id' get-inbox-thread returns while the description calls it 'Email ID'.

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 and resource ('Read one message in a Resend inbox thread, body included') and immediately enumerates what that includes (html/text bodies, addresses, Message-ID, attachments). The 'NOT for' section names the exact sibling tools that cover the adjacent cases, so the agent can disambiguate without opening a 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?

Explicit when-to-use and when-not-to-use guidance: names get-inbox-thread, get-email, and get-received-email as alternatives with the condition that selects each. It also documents the handoff workflow ('get-inbox-thread points here for a body... pass it as emailId'), which is exactly the routing information an agent needs.

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