Skip to main content
Glama

delete_draft

Remove unwanted draft emails from Gmail by specifying the draft ID to clear space and maintain organization.

Instructions

Delete a draft

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the draft to delete

Implementation Reference

  • Handler function that executes the delete_draft tool: wraps the Gmail API call to delete a draft by ID using the shared handleTool utility.
    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 delete_draft tool using Zod: requires 'id' string parameter.
    {
      id: z.string().describe("The ID of the draft to delete")
    },
  • src/index.ts:265-276 (registration)
    Registration of the delete_draft tool on the MCP server, defining name, description, schema, and handler.
    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)
        })
      }
    )
  • Shared helper function handleTool used by delete_draft (and other tools) to handle OAuth2 authentication, client creation, and API call execution 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}`
      }
    }
  • Shared helper to format tool responses as MCP content blocks.
    const formatResponse = (response: any) => ({ content: [{ type: "text", text: JSON.stringify(response) }] })
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Delete a draft' implies a destructive, irreversible mutation, but it does not specify permissions required, side effects (e.g., if deletion is permanent or recoverable), error conditions, or response behavior. This is inadequate for a mutation tool with zero annotation coverage.

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 with just three words, front-loading the core action ('Delete a draft'). There is no wasted language, making it efficient for quick comprehension, though this brevity contributes to gaps in other dimensions like guidelines and transparency.

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 destructive nature, lack of annotations, and no output schema, the description is incomplete. It does not address critical context such as success/error responses, idempotency, or comparison to sibling tools. For a mutation tool with potential side effects, more detail is needed to guide safe and correct usage.

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, with the 'id' parameter clearly documented. The description adds no additional meaning beyond the schema, such as format examples (e.g., draft ID format) or constraints. Since schema coverage is high, the baseline score of 3 is appropriate, as the schema handles parameter documentation adequately.

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

Purpose3/5

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

The description 'Delete a draft' clearly states the verb ('delete') and resource ('draft'), making the purpose understandable. However, it lacks specificity about what a 'draft' entails (e.g., email draft in Gmail) and does not differentiate from sibling tools like 'delete_message' or 'delete_thread', which are similar deletion operations on different resources.

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 does not mention prerequisites (e.g., needing an existing draft ID), exclusions (e.g., cannot delete sent drafts), or compare to siblings like 'delete_message' or 'trash_message'. This leaves the agent without context for tool selection.

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