Skip to main content
Glama

delete_send_as

Remove a specified send-as alias from your Gmail account to simplify email management and maintain accurate sender identities.

Instructions

Deletes the specified send-as alias

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sendAsEmailYesThe send-as alias to be deleted

Implementation Reference

  • src/index.ts:1145-1156 (registration)
    Registration of the 'delete_send_as' tool using McpServer.tool(), including schema definition and inline handler function that calls the Gmail API to delete the specified send-as alias.
    server.tool("delete_send_as",
      "Deletes the specified send-as alias",
      {
        sendAsEmail: z.string().describe("The send-as alias to be deleted")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.sendAs.delete({ userId: 'me', sendAsEmail: params.sendAsEmail })
          return formatResponse(data)
        })
      }
    )
  • Handler function for 'delete_send_as' tool. Uses handleTool wrapper to authenticate and execute Gmail API call: gmail.users.settings.sendAs.delete() with userId 'me' and the provided sendAsEmail.
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.sendAs.delete({ userId: 'me', sendAsEmail: params.sendAsEmail })
          return formatResponse(data)
        })
      }
    )
  • Input schema for 'delete_send_as' tool using Zod: requires 'sendAsEmail' as string.
    {
      sendAsEmail: z.string().describe("The send-as alias to be deleted")
    },
  • Shared helper function 'handleTool' used by all Gmail tools, including 'delete_send_as'. Handles OAuth2 authentication, client creation, API call execution, and error handling (esp. auth errors).
    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) {
        // Check for specific authentication errors
        if (
          error.message?.includes("invalid_grant") ||
          error.message?.includes("refresh_token") ||
          error.message?.includes("invalid_client") ||
          error.message?.includes("unauthorized_client") ||
          error.code === 401 ||
          error.code === 403
        ) {
          return formatResponse({
            error: `Authentication failed: ${error.message}. Please re-authenticate by running: npx @shinzolabs/gmail-mcp auth`,
          });
        }
    
        return formatResponse({ error: `Tool execution failed: ${error.message}` });
      }
    }
  • Utility helper 'formatResponse' used by all tools to format API responses into MCP content format (JSON stringified).
    const formatResponse = (response: any) => ({ content: [{ type: "text", text: JSON.stringify(response) }] })

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

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