Skip to main content
Glama

update_imap

Configure IMAP access for Gmail accounts by enabling or 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:868-881 (registration)
    Registration of the 'update_imap' MCP tool, including input schema validation with Zod and the handler function that uses handleTool to authenticate and call 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)
        })
      }
    )
  • The handler function for the 'update_imap' tool, which invokes the shared handleTool utility to manage OAuth2 authentication and execute the Gmail users.settings.updateImap API call with the provided parameters.
      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 the 'update_imap' tool defined using Zod, specifying parameters for enabling IMAP, expunge behavior, and maximum folder size.
    {
      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 'update_imap' (and other tools) to handle OAuth2 client creation, credential validation, Gmail client instantiation, 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}`
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Updates IMAP settings' implies a mutation operation but doesn't disclose permission requirements, whether changes are reversible, potential side effects, rate limits, or what happens to existing settings not mentioned. This is inadequate for a mutation tool with zero annotation coverage.

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 extremely concise at just three words, with zero wasted language. It's front-loaded with the essential action and resource. Every word earns its place, making it highly efficient despite its limitations in 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?

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what the tool returns, what permissions are needed, potential side effects, or how it relates to other settings tools. The 100% schema coverage helps with parameters but doesn't compensate for the lack of behavioral and contextual information.

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?

Schema description coverage is 100%, so the schema already documents all three parameters thoroughly. The description adds no additional parameter information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 basic purpose understandable. However, it lacks specificity about what aspects of IMAP settings are updated and doesn't differentiate from potential sibling tools like 'update_pop' or 'update_auto_forwarding' that also update settings.

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. There's no mention of prerequisites, when this operation is appropriate, or what distinguishes it from other settings update tools like 'update_pop' or 'update_auto_forwarding' in the sibling list.

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

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