Skip to main content
Glama

list_smime_info

Retrieve S/MIME encryption configurations for a specific Gmail sender alias to manage email security settings.

Instructions

Lists S/MIME configs for the specified send-as alias

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sendAsEmailYesThe email address that appears in the 'From:' header

Implementation Reference

  • src/index.ts:1276-1287 (registration)
    Registration of the 'list_smime_info' tool, including description, input schema, and inline handler function that lists S/MIME configurations for a given send-as email using the Gmail API.
    server.tool("list_smime_info", "Lists S/MIME configs for the specified send-as alias", { sendAsEmail: z.string().describe("The email address that appears in the 'From:' header") }, async (params) => { return handleTool(config, async (gmail: gmail_v1.Gmail) => { const { data } = await gmail.users.settings.sendAs.smimeInfo.list({ userId: 'me', sendAsEmail: params.sendAsEmail }) return formatResponse(data) }) } )
  • Handler function for 'list_smime_info' tool. Validates auth via handleTool, calls Gmail API to list S/MIME info for the specified sendAsEmail, and formats the response.
    async (params) => { return handleTool(config, async (gmail: gmail_v1.Gmail) => { const { data } = await gmail.users.settings.sendAs.smimeInfo.list({ userId: 'me', sendAsEmail: params.sendAsEmail }) return formatResponse(data) }) }
  • Input schema for 'list_smime_info' tool defining the required 'sendAsEmail' parameter.
    { sendAsEmail: z.string().describe("The email address that appears in the 'From:' header") },
  • Shared 'handleTool' helper used by 'list_smime_info' (and other tools) for OAuth2 authentication validation, Gmail client creation, API call execution, and error handling with specific auth error responses.
    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 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/faithk7/gmail-mcp'

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