Skip to main content
Glama

update_imap

Configure IMAP access for Gmail accounts by enabling/disabling the protocol, setting message deletion behavior, and managing folder size limits.

Instructions

Updates IMAP settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enabledYesWhether IMAP is enabled for the account
expungeBehaviorNoThe action that will be executed on a message when it is marked as deleted and expunged from the last visible IMAP folder
maxFolderSizeNoAn optional limit on the number of messages that can be accessed through IMAP

Implementation Reference

  • src/index.ts:887-900 (registration)
    Registration of the 'update_imap' tool, including schema definition and inline handler function that calls the Gmail API to update IMAP settings.
    server.tool("update_imap",
      "Updates IMAP settings",
      {
        enabled: z.boolean().describe("Whether IMAP is enabled for the account"),
        expungeBehavior: z.enum(['archive', 'trash', 'deleteForever']).optional().describe("The action that will be executed on a message when it is marked as deleted and expunged from the last visible IMAP folder"),
        maxFolderSize: z.number().optional().describe("An optional limit on the number of messages that can be accessed through IMAP")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.updateImap({ userId: 'me', requestBody: params })
          return formatResponse(data)
        })
      }
    )
  • Handler function for 'update_imap' tool: authenticates via handleTool, calls gmail.users.settings.updateImap with userId 'me' and requestBody params, formats and returns the response.
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.updateImap({ userId: 'me', requestBody: params })
          return formatResponse(data)
        })
      }
    )
  • Input schema for 'update_imap' tool using Zod: enabled (boolean, required), expungeBehavior (enum, optional), maxFolderSize (number, optional).
    {
      enabled: z.boolean().describe("Whether IMAP is enabled for the account"),
      expungeBehavior: z.enum(['archive', 'trash', 'deleteForever']).optional().describe("The action that will be executed on a message when it is marked as deleted and expunged from the last visible IMAP folder"),
      maxFolderSize: z.number().optional().describe("An optional limit on the number of messages that can be accessed through IMAP")
    },
  • Shared helper function handleTool used by all Gmail API tools, including update_imap: handles OAuth2 authentication, client creation, and executes the provided apiCall 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}`
      }
    }
  • Helper function formatResponse used by update_imap handler to format API responses as MCP content blocks.
    const formatResponse = (response: any) => ({ content: [{ type: "text", text: JSON.stringify(response) }] })
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must fully disclose behavioral traits. 'Updates IMAP settings' implies a mutation operation, but it doesn't specify whether this requires authentication, affects email delivery, has side effects (e.g., disrupting existing connections), or provides confirmation. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste—'Updates IMAP settings' is front-loaded and directly states the action. It's appropriately sized for a tool with a clear name and well-documented schema, though it could benefit from more detail to improve other dimensions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (a mutation operation with no annotations and no output schema), the description is incomplete. It doesn't explain what 'IMAP settings' entail, the impact of updates, or what the tool returns. With no annotations to cover safety or behavior, and no output schema, the description should provide more context to guide the agent effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with clear documentation for all three parameters (enabled, expungeBehavior, maxFolderSize). The description adds no additional meaning beyond the schema, such as explaining relationships between parameters or usage examples. With high schema coverage, the baseline score of 3 is appropriate, as the schema handles the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Updates IMAP settings' clearly states the verb ('Updates') and resource ('IMAP settings'), making the purpose understandable. However, it's vague about what specific settings are updated and doesn't differentiate from sibling tools like 'update_pop' or 'update_auto_forwarding' that also update settings. It's not tautological but lacks specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing admin access), when it's appropriate (e.g., configuring email clients), or exclusions (e.g., not for POP settings). With many sibling tools for updating various settings, this omission leaves the agent without context for selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

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/nk900600/gmail-mcp'

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