Skip to main content
Glama

delete_thread

Remove unwanted email conversations from Gmail by deleting entire threads using their unique ID. This tool helps manage your inbox by permanently eliminating selected email threads.

Instructions

Delete a thread

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe ID of the thread to delete

Implementation Reference

  • The handler function for the 'delete_thread' tool. It uses handleTool to perform OAuth2 authentication and executes the Gmail API call to permanently delete the specified thread by ID.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.threads.delete({ userId: 'me', id: params.id })
        return formatResponse(data)
      })
    }
  • The input schema for the 'delete_thread' tool, defining the required 'id' parameter as a string using Zod validation.
    {
      id: z.string().describe("The ID of the thread to delete")
    },
  • src/index.ts:702-713 (registration)
    The registration of the 'delete_thread' tool on the MCP server, including name, description, schema, and handler function.
    server.tool("delete_thread",
      "Delete a thread",
      {
        id: z.string().describe("The ID of the thread to delete")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.threads.delete({ userId: 'me', id: params.id })
          return formatResponse(data)
        })
      }
    )
  • Shared helper function used by 'delete_thread' (and other tools) to handle OAuth2 client setup, credential validation, Gmail client creation, and execution of 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}`
      }
    }
  • Helper function used by 'delete_thread' (and other tools) to format the API response into MCP-compatible content structure.
    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?

With no annotations provided, the description carries full burden for behavioral disclosure. 'Delete a thread' implies a destructive operation, but doesn't specify whether this is permanent or reversible, what permissions are required, whether it affects associated messages, or what happens on success/failure. This is inadequate for a destructive 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 at just three words, with zero wasted language. It's front-loaded with the core action and resource, though this brevity comes at the cost of completeness. Every word earns its place in conveying the basic operation.

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 operation with no annotations and no output schema, the description is severely incomplete. It doesn't explain what 'delete' means in this context (permanent vs. reversible), what happens to associated messages, what permissions are required, or what the tool returns. Given the complexity of deletion operations and lack of structured metadata, this description provides insufficient context.

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%, with the single parameter 'id' clearly documented as 'The ID of the thread to delete'. The description adds no additional parameter information beyond what's already in the schema, which is acceptable given the high schema coverage. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 thread' is a tautology that restates the tool name without adding meaningful context. It specifies the verb (delete) and resource (thread), but doesn't distinguish this from sibling tools like 'trash_thread' or 'delete_message', leaving ambiguity about what type of deletion this performs.

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?

No guidance is provided about when to use this tool versus alternatives like 'trash_thread' or 'delete_message'. The description offers no context about prerequisites, permissions needed, or appropriate scenarios for this deletion operation versus other thread-related tools.

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