update_pop
Configure POP email access settings to control which messages are retrievable and what happens to them after fetching.
Instructions
Updates POP settings
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| accessWindow | Yes | The range of messages which are accessible via POP | |
| disposition | Yes | The action that will be executed on a message after it has been fetched via POP |
Implementation Reference
- src/index.ts:896-908 (registration)Registration of the MCP tool 'update_pop' including description, input schema, and handler function.
server.tool("update_pop", "Updates POP settings", { accessWindow: z.enum(['disabled', 'allMail', 'fromNowOn']).describe("The range of messages which are accessible via POP"), disposition: z.enum(['archive', 'trash', 'leaveInInbox']).describe("The action that will be executed on a message after it has been fetched via POP") }, async (params) => { return handleTool(config, async (gmail: gmail_v1.Gmail) => { const { data } = await gmail.users.settings.updatePop({ userId: 'me', requestBody: params }) return formatResponse(data) }) } ) - src/index.ts:902-907 (handler)The handler function executes the tool logic: authenticates via handleTool, calls Gmail API to update POP settings with provided params, formats and returns the response.
async (params) => { return handleTool(config, async (gmail: gmail_v1.Gmail) => { const { data } = await gmail.users.settings.updatePop({ userId: 'me', requestBody: params }) return formatResponse(data) }) } - src/index.ts:898-901 (schema)Zod schema defining input parameters for 'update_pop': accessWindow (enum) and disposition (enum).
{ accessWindow: z.enum(['disabled', 'allMail', 'fromNowOn']).describe("The range of messages which are accessible via POP"), disposition: z.enum(['archive', 'trash', 'leaveInInbox']).describe("The action that will be executed on a message after it has been fetched via POP") }, - src/index.ts:49-65 (helper)Shared helper function 'handleTool' used by 'update_pop' and other tools to handle OAuth2 authentication, Gmail client creation, and API call execution with error handling.
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) { return `Tool execution failed: ${error.message}` } } - src/index.ts:47-47 (helper)Shared helper 'formatResponse' used to format API responses into MCP content structure.
const formatResponse = (response: any) => ({ content: [{ type: "text", text: JSON.stringify(response) }] })