Skip to main content
Glama

list_drafts

Retrieve draft emails from Gmail with options to filter by search query, limit results, and include content from spam/trash folders.

Instructions

List drafts in the user's mailbox

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxResultsNoMaximum number of drafts to return. Accepts values between 1-500
qNoOnly return drafts matching the specified query. Supports the same query format as the Gmail search box
includeSpamTrashNoInclude drafts from SPAM and TRASH in the results
includeBodyHtmlNoWhether to include the parsed HTML in the return for each body, excluded by default because they can be excessively large

Implementation Reference

  • Handler function for the 'list_drafts' tool. Fetches drafts from Gmail API with pagination, processes message payloads to decode bodies and filter headers, and returns formatted response.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        let drafts: Draft[] = []
    
        const { data } = await gmail.users.drafts.list({ userId: 'me', ...params })
    
        drafts.push(...data.drafts || [])
    
        while (data.nextPageToken) {
          const { data: nextData } = await gmail.users.drafts.list({ userId: 'me', ...params, pageToken: data.nextPageToken })
          drafts.push(...nextData.drafts || [])
        }
    
        if (drafts) {
          drafts = drafts.map(draft => {
            if (draft.message?.payload) {
              draft.message.payload = processMessagePart(
                draft.message.payload,
                params.includeBodyHtml
              )
            }
            return draft
          })
        }
    
        return formatResponse(drafts)
      })
    }
  • Input schema for 'list_drafts' tool using Zod validation: parameters for maxResults, query (q), includeSpamTrash, and includeBodyHtml.
      maxResults: z.number().optional().describe("Maximum number of drafts to return. Accepts values between 1-500"),
      q: z.string().optional().describe("Only return drafts matching the specified query. Supports the same query format as the Gmail search box"),
      includeSpamTrash: z.boolean().optional().describe("Include drafts from SPAM and TRASH in the results"),
      includeBodyHtml: z.boolean().optional().describe("Whether to include the parsed HTML in the return for each body, excluded by default because they can be excessively large"),
    },
  • src/index.ts:319-355 (registration)
    Registration of the 'list_drafts' tool on the MCP server, including name, description, input schema, and handler function.
    server.tool("list_drafts",
      "List drafts in the user's mailbox",
      {
        maxResults: z.number().optional().describe("Maximum number of drafts to return. Accepts values between 1-500"),
        q: z.string().optional().describe("Only return drafts matching the specified query. Supports the same query format as the Gmail search box"),
        includeSpamTrash: z.boolean().optional().describe("Include drafts from SPAM and TRASH in the results"),
        includeBodyHtml: z.boolean().optional().describe("Whether to include the parsed HTML in the return for each body, excluded by default because they can be excessively large"),
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          let drafts: Draft[] = []
    
          const { data } = await gmail.users.drafts.list({ userId: 'me', ...params })
    
          drafts.push(...data.drafts || [])
    
          while (data.nextPageToken) {
            const { data: nextData } = await gmail.users.drafts.list({ userId: 'me', ...params, pageToken: data.nextPageToken })
            drafts.push(...nextData.drafts || [])
          }
    
          if (drafts) {
            drafts = drafts.map(draft => {
              if (draft.message?.payload) {
                draft.message.payload = processMessagePart(
                  draft.message.payload,
                  params.includeBodyHtml
                )
              }
              return draft
            })
          }
    
          return formatResponse(drafts)
        })
      }
    )
  • Helper function used by list_drafts to process message parts: decodes base64 bodies for text/plain or html(if specified), recursively processes parts, and filters headers.
    const processMessagePart = (messagePart: MessagePart, includeBodyHtml = false): MessagePart => {
      if ((messagePart.mimeType !== 'text/html' || includeBodyHtml) && messagePart.body) {
        messagePart.body = decodedBody(messagePart.body)
      }
    
      if (messagePart.parts) {
        messagePart.parts = messagePart.parts.map(part => processMessagePart(part, includeBodyHtml))
      }
    
      if (messagePart.headers) {
        messagePart.headers = messagePart.headers.filter(header => RESPONSE_HEADERS_LIST.includes(header.name || ''))
      }
    
      return messagePart
    }
  • Shared helper function for all Gmail tools, including list_drafts: handles OAuth2 authentication, client creation, and executes the API call with error handling.
    const handleTool = async (queryConfig: Record<string, any> | undefined, apiCall: (gmail: gmail_v1.Gmail) => Promise<any>) => {
      try {
        const oauth2Client = queryConfig ? createOAuth2Client(queryConfig) : defaultOAuth2Client
        if (!oauth2Client) throw new Error('OAuth2 client could not be created, please check your credentials')
    
        const credentialsAreValid = await validateCredentials(oauth2Client)
        if (!credentialsAreValid) throw new Error('OAuth2 credentials are invalid, please re-authenticate')
    
        const gmailClient = queryConfig ? google.gmail({ version: 'v1', auth: oauth2Client }) : defaultGmailClient
        if (!gmailClient) throw new Error('Gmail client could not be created, please check your credentials')
    
        const result = await apiCall(gmailClient)
        return result
      } catch (error: any) {
        return `Tool execution failed: ${error.message}`
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions that drafts are listed from 'the user's mailbox' which implies personal scope, but fails to describe important behaviors like whether this is a read-only operation, how results are ordered/paginated, authentication requirements, or rate limits. For a list operation with zero annotation coverage, this leaves significant gaps.

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 a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for a list operation and front-loads the essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a list operation with 4 parameters and no output schema, the description is insufficient. It doesn't explain what the return format looks like (e.g., list of draft objects with IDs, subjects), doesn't mention pagination behavior, and provides no context about authentication or error conditions. The lack of annotations exacerbates these gaps.

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?

The description provides no parameter information, but the input schema has 100% description coverage with clear documentation for all 4 parameters. This meets the baseline score of 3 where the schema does the heavy lifting, though the description adds no value beyond what's already in the structured schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('List') and resource ('drafts in the user's mailbox'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'list_messages' or 'list_threads' that also list mailbox content, which prevents a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'list_messages' or 'get_draft', nor does it mention any prerequisites or constraints. It simply states what the tool does without contextual usage information.

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/nk900600/gmail-mcp'

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