Skip to main content
Glama

list_send_as

Retrieve all send-as email aliases associated with a Gmail account to manage and verify custom sender addresses effectively.

Instructions

Lists the send-as aliases for the specified account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:1171-1180 (registration)
    Registers the 'list_send_as' MCP tool. The inline schema accepts no parameters. The handler uses the shared 'handleTool' helper to authenticate and call the Gmail API's users.settings.sendAs.list method to retrieve the list of send-as aliases, then formats the response.
    server.tool("list_send_as", "Lists the send-as aliases for the specified account", {}, async () => { return handleTool(config, async (gmail: gmail_v1.Gmail) => { const { data } = await gmail.users.settings.sendAs.list({ userId: 'me' }) return formatResponse(data) }) } )
  • The handler function for 'list_send_as' tool execution, which delegates to handleTool for auth and API call to list send-as aliases.
    async () => { return handleTool(config, async (gmail: gmail_v1.Gmail) => { const { data } = await gmail.users.settings.sendAs.list({ userId: 'me' }) return formatResponse(data) }) }
  • Shared helper function 'handleTool' that manages OAuth2 authentication, creates Gmail client, executes the provided API callback, handles errors (especially auth), and formats responses. Used by 'list_send_as' and all other Gmail tools.
    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 function to format tool responses as MCP content blocks with JSON stringified data.
    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