Skip to main content
Glama

delete_draft

Remove unwanted draft emails from Gmail by specifying the draft ID to clear your drafts folder and maintain organized email management.

Instructions

Delete a draft

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the draft to delete

Implementation Reference

  • src/index.ts:284-295 (registration)
    Registration of the 'delete_draft' tool with schema and inline handler function.
    server.tool("delete_draft",
      "Delete a draft",
      {
        id: z.string().describe("The ID of the draft to delete")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.drafts.delete({ userId: 'me', id: params.id })
          return formatResponse(data)
        })
      }
    )
  • Handler function that executes the deletion of a Gmail draft by ID using the Gmail API.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.drafts.delete({ userId: 'me', id: params.id })
        return formatResponse(data)
      })
    }
  • Input schema for the delete_draft tool, requiring a draft ID string.
    {
      id: z.string().describe("The ID of the draft to delete")
    },
  • Shared helper function handleTool used by delete_draft and other tools to handle OAuth2 authentication and Gmail 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}`
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Delete a draft' implies a destructive mutation, but it doesn't specify whether this is permanent or reversible, what permissions are required, whether it's synchronous or asynchronous, or what happens on success/failure. For a destructive operation with zero annotation coverage, this leaves critical behavioral traits undisclosed.

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 extremely concise at just three words, with zero wasted language. It's front-loaded with the core action and resource. While under-specified for completeness, it achieves perfect conciseness by eliminating all unnecessary verbiage.

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 destructive mutation tool with no annotations and no output schema, the description is severely incomplete. It doesn't explain what 'delete' means operationally, what the expected outcome is, error conditions, or how this differs from similar deletion/trash operations among siblings. The agent lacks sufficient context to use this tool safely and effectively.

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?

With 100% schema description coverage for the single parameter 'id', the schema already fully documents the parameter's purpose and type. The description doesn't add any parameter-specific information beyond what's in the schema, but since there's only one well-documented parameter, this doesn't create a significant gap. The baseline for high schema coverage with minimal parameters is appropriately met.

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

Purpose2/5

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

The description 'Delete a draft' is essentially a tautology that restates the tool name with minimal elaboration. It specifies the verb ('Delete') and resource ('a draft'), but lacks any distinguishing details about scope, permanence, or effects that would differentiate it from similar tools like delete_message or trash_message. This provides only basic purpose identification without meaningful context.

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

Usage Guidelines1/5

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

The description offers no guidance on when to use this tool versus alternatives. With sibling tools like delete_message, trash_message, and delete_thread available, there's no indication of whether this is for permanent deletion versus reversible actions, whether it applies to drafts specifically versus other message types, or any prerequisites. The agent receives zero usage context.

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