Skip to main content
Glama
Sign In
Email Sending MCP

Email Sending MCP

by resend
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Inbox Drafts

list-inbox-drafts
Read-only

List all unsent drafts in a Resend inbox with their IDs to check what messages are composed but not sent and to get draft IDs for other tools.

Instructions

Purpose: List the drafts in one Resend inbox (the messages composed there but not sent), each with its ID.

NOT for: Reading a draft's body (use get-inbox-draft) or sending one (use send-inbox-draft). Not for the messages already in a thread (use get-inbox-thread), and not for sent emails (use list-emails).

Returns: For each draft: id, type ("standalone" or "reply"), to, cc, bcc, subject, snippet, thread_id, reply_to_email_id, attachments, updated_at.

When to use: User asks what drafts an inbox holds, or you need a draft ID. A "reply" draft answers a message in a thread and carries that thread_id; a "standalone" draft is a new message belonging to no thread. Get the inbox ID from list-inboxes, then the draft ID from here for get-inbox-draft, update-inbox-draft, send-inbox-draft, or remove-inbox-draft. This endpoint is paginated: when more drafts exist, pass the last draft's ID back as "after". When paging backward with "before", pass the first draft's ID back as "before".

Input Schema

NameRequiredDescriptionDefault
afterNoDraft ID after which to retrieve more (for the next, older page). Cannot be used with "before". An ID that is not an unsent draft on this inbox returns a 404.
limitNoNumber of drafts to retrieve. Default: 20, Max: 100, Min: 1
beforeNoDraft ID before which to retrieve more (for the previous, newer page). Cannot be used with "after". An ID that is not an unsent draft on this inbox returns a 404.
inboxIdYesInbox ID, or the inbox email address (e.g. "support@example.com"). Not the Resend receiving address.

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.7/5.0
Behavior5/5

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

Annotations already establish read-only, non-destructive, closed-world safety. The description adds substantial behavioral context beyond annotations: pagination mechanics with after/before, the standalone vs. reply draft distinction and thread_id relationship, and the exact return fields. No contradiction with annotations is present.

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?

The description is front-loaded with purpose, then structured into Not for, Returns, and When to use. Every section adds decision-relevant information: sibling routing, return shape, and pagination usage. It is longer than a one-liner but not wasteful.

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 paginated list tool with four parameters, no output schema, and clear annotations, the description covers everything an agent needs: scope, alternatives, return fields, pagination instructions, and ID sourcing. No critical gap remains.

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 every parameter including after, before, limit, and inboxId. The description's pagination notes largely mirror the schema's own parameter descriptions, adding only light operational framing rather than new parameter syntax or constraints.

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 states a specific verb and resource: 'List the drafts in one Resend inbox... each with its ID.' It then explicitly distinguishes this tool from get-inbox-draft, send-inbox-draft, get-inbox-thread, and list-emails, so an agent can route correctly without opening schemas.

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 explicit when-to-use guidance ('User asks what drafts an inbox holds, or you need a draft ID') and explicit not-for guidance naming four alternative tools. It also explains the prerequisite chain (get inbox ID from list-inboxes) and downstream uses of the returned draft ID.

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