Skip to main content
Glama

list_drafts

Retrieve draft emails from your Gmail mailbox with customizable filters for search queries, result limits, and content inclusion.

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

  • The handler function for the 'list_drafts' tool. It uses the Gmail API to list drafts with pagination support, processes each draft's message payload (decoding bodies and filtering headers), and returns a 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)
      })
    }
  • Zod schema defining the input parameters for the 'list_drafts' tool.
    {
      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:300-336 (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 'handleTool' used by 'list_drafts' to manage OAuth2 authentication, Gmail client creation, and error handling around API calls.
    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}`
      }
    }
  • Helper function 'processMessagePart' used to decode message bodies, recursively process parts, and filter headers in drafts.
    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
    }
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 but provides minimal information. It states it's a list operation but doesn't describe return format, pagination behavior, ordering, rate limits, authentication requirements, or whether it's a read-only operation. The description doesn't contradict any annotations (since none exist), but fails to provide essential behavioral context for a tool with 4 parameters.

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 gets straight to the point with zero wasted words. It's appropriately sized for a list operation and front-loads the essential information. Every word earns its place in this minimal but complete statement of function.

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?

Given the tool's complexity (4 parameters, no output schema, no annotations), the description is insufficiently complete. It doesn't explain what the tool returns (draft objects with what fields?), doesn't mention pagination or ordering behavior, and provides no context about authentication or rate limits. For a tool with multiple filtering parameters and no output schema, the description should provide more guidance about expected results and usage patterns.

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 input schema has 100% description coverage, so all parameters are well-documented in the schema itself. The description adds no parameter-specific information beyond what's already in the schema descriptions. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description, which applies here.

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 action ('List') and resource ('drafts in the user's mailbox'), making the purpose immediately understandable. It distinguishes this tool from other list tools like list_messages or list_threads by specifying 'drafts' as the resource type. However, it doesn't explicitly differentiate from get_draft (singular) or mention that this returns multiple drafts.

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. It doesn't mention when to use list_drafts versus list_messages (which might include drafts), get_draft (for a single draft), or create_draft. There's no context about prerequisites, permissions needed, or typical use cases for listing drafts versus other message types.

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

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