Skip to main content
Glama

verify_send_as

Verify a send-as email alias by sending a confirmation email to ensure the alias is valid and can be used for sending messages through Gmail MCP.

Instructions

Sends a verification email to the specified send-as alias

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sendAsEmailYesThe send-as alias to be verified

Implementation Reference

  • src/index.ts:1220-1231 (registration)
    Registration of the verify_send_as MCP tool, defining its schema (input: sendAsEmail string) and handler which sends a verification email via the Gmail API's users.settings.sendAs.verify method, wrapped in handleTool for auth handling.
    server.tool("verify_send_as", "Sends a verification email to the specified send-as alias", { sendAsEmail: z.string().describe("The send-as alias to be verified") }, async (params) => { return handleTool(config, async (gmail: gmail_v1.Gmail) => { const { data } = await gmail.users.settings.sendAs.verify({ userId: 'me', sendAsEmail: params.sendAsEmail }) return formatResponse(data) }) } )
  • Handler function for verify_send_as tool: authenticates via handleTool, calls Gmail API to verify send-as alias by sending email.
    async (params) => { return handleTool(config, async (gmail: gmail_v1.Gmail) => { const { data } = await gmail.users.settings.sendAs.verify({ userId: 'me', sendAsEmail: params.sendAsEmail }) return formatResponse(data) }) }
  • Input schema for verify_send_as tool: requires sendAsEmail as string.
    { sendAsEmail: z.string().describe("The send-as alias to be verified") },
  • Shared helper function handleTool used by all tools, including verify_send_as, to handle OAuth2 authentication, client creation, and error handling before executing the API call.
    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}` }); } }
  • Helper to format tool responses as MCP content blocks.
    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