Skip to main content
Glama
resend

Email Sending MCP

by resend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Inbox Thread

get-inbox-thread
Read-only

Purpose: Get one thread in a Resend inbox: the thread itself plus the metadata of its emails, oldest first.

Instructions

Purpose: Get one thread in a Resend inbox: the thread itself plus the metadata of its emails, oldest first.

NOT for: Reading a message's body. This tool returns no html or text, because a whole conversation's bodies would flood the response. Use get-inbox-thread-email for one message's body.

Returns: The thread's id, subject, folder, labels and read state, then for each email its email ID, direction (inbound or outbound), from, to, subject, received_at, read state, and how many attachments it carries. Emails are paginated: when more exist, pass the last email's ID back as "after". When paging backward with "before", pass the first email's ID back as "before".

When to use: User wants to see a conversation, or you need a message's email ID. A message's ID IS the email ID that get-inbox-thread-email, reply-to-inbox-thread-email, and forward-inbox-thread-email take as their "emailId". Get the thread ID from list-inbox-threads or search-inbox-threads.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoEmail ID after which to retrieve more (the next, newer page). Cannot be used with "before". An ID that is not a message of this thread returns a 404.
limitNoNumber of emails to retrieve. Default: 100, Max: 100, Min: 1. Emails are oldest first.
beforeNoEmail ID before which to retrieve more (the previous, older page). Cannot be used with "after". An ID that is not a message of this thread returns a 404.
inboxIdYesInbox ID
threadIdYesThread ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.26.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover only safety (readOnly, non-destructive, closed-world). The description adds the behavior that matters for this call: no html/text bodies are returned, emails come oldest first, results are paginated with 'after'/'before' cursor semantics. With no output schema present, this return-shape disclosure is essential and is supplied.

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?

It is long but well-structured with bolded Purpose / NOT for / Returns / When to use headers and is front-loaded so an agent can triage quickly. The Returns paragraph is dense but each field listed carries routing value; only slight trimming is possible.

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?

For a read-only paginated fetch with no output schema, the description fully covers what is returned, what is deliberately excluded, pagination mechanics, and ID provenance. Nothing needed to call it correctly is missing.

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 coverage is 100%, so the baseline is 3, and the schema already documents after/before/limit including the 404 on foreign IDs. The description goes marginally beyond by explaining the cursor workflow ('pass the last email's ID back as "after"', pass the first for 'before'), which helps an agent page correctly.

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 opens with a precise verb+resource: 'Get one thread in a Resend inbox: the thread itself plus the metadata of its emails, oldest first.' It explicitly scopes what is and is not included (metadata only, no bodies), and names the sibling it must be distinguished from (get-inbox-thread-email).

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?

It provides an explicit 'NOT for' clause routing body-reading to get-inbox-thread-email, a 'When to use' clause, and tells the agent where the thread ID comes from (list-inbox-threads / search-inbox-threads) and how the returned email ID feeds get-inbox-thread-email, reply-to-inbox-thread-email, and forward-inbox-thread-email.

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