Skip to main content
Glama

delete_forwarding_address

Remove a specified email forwarding address to stop automated message redirection. Simplifies managing email workflows and ensures control over message delivery paths.

Instructions

Deletes the specified forwarding address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forwardingEmailYesThe forwarding address to be deleted

Implementation Reference

  • src/index.ts:1090-1101 (registration)
    Registration of the 'delete_forwarding_address' tool, including schema and inline handler function that deletes the forwarding address via Gmail API
    server.tool("delete_forwarding_address", "Deletes the specified forwarding address", { forwardingEmail: z.string().describe("The forwarding address to be deleted") }, async (params) => { return handleTool(config, async (gmail: gmail_v1.Gmail) => { const { data } = await gmail.users.settings.forwardingAddresses.delete({ userId: 'me', forwardingEmail: params.forwardingEmail }) return formatResponse(data) }) } )
  • Handler function for delete_forwarding_address tool: validates auth via handleTool, calls Gmail API to delete the specified forwarding address
    async (params) => { return handleTool(config, async (gmail: gmail_v1.Gmail) => { const { data } = await gmail.users.settings.forwardingAddresses.delete({ userId: 'me', forwardingEmail: params.forwardingEmail }) return formatResponse(data) }) }
  • Input schema for delete_forwarding_address tool: requires forwardingEmail string
    { forwardingEmail: z.string().describe("The forwarding address to be deleted") },
  • Shared handleTool helper used by all tools, including delete_forwarding_address: handles OAuth2 client creation, credential validation, Gmail client setup, and error handling for auth issues
    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}` }); } }
  • Shared formatResponse helper used by delete_forwarding_address handler to format the API response as MCP content
    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