Skip to main content
Glama

watch_mailbox

Monitor Gmail mailbox for new emails or changes by setting up real-time notifications through Cloud Pub/Sub topics, with optional label filtering.

Instructions

Watch for changes to the user's mailbox

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNameYesThe name of the Cloud Pub/Sub topic to publish notifications to
labelIdsNoLabel IDs to restrict notifications to
labelFilterActionNoWhether to include or exclude the specified labels

Implementation Reference

  • src/index.ts:1281-1294 (registration)
    Registration of the 'watch_mailbox' tool with input schema using Zod and handler function that uses the shared handleTool to call Gmail API's users.watch method for watching mailbox changes.
    server.tool("watch_mailbox",
      "Watch for changes to the user's mailbox",
      {
        topicName: z.string().describe("The name of the Cloud Pub/Sub topic to publish notifications to"),
        labelIds: z.array(z.string()).optional().describe("Label IDs to restrict notifications to"),
        labelFilterAction: z.enum(['include', 'exclude']).optional().describe("Whether to include or exclude the specified labels")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.watch({ userId: 'me', requestBody: params })
          return formatResponse(data)
        })
      }
    )
  • Input schema for the 'watch_mailbox' tool defining parameters for Pub/Sub topic and label filtering.
    {
      topicName: z.string().describe("The name of the Cloud Pub/Sub topic to publish notifications to"),
      labelIds: z.array(z.string()).optional().describe("Label IDs to restrict notifications to"),
      labelFilterAction: z.enum(['include', 'exclude']).optional().describe("Whether to include or exclude the specified labels")
    },
  • Handler function for 'watch_mailbox' tool that invokes the Gmail API watch endpoint via the shared handleTool utility.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.watch({ userId: 'me', requestBody: params })
        return formatResponse(data)
      })
    }
  • Shared helper function used by all Gmail tools, including 'watch_mailbox', to handle OAuth2 authentication, client creation, and API call execution.
    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, the description carries full burden but only states 'watch for changes' without disclosing behavioral traits. It doesn't explain that this likely creates a subscription, involves real-time notifications, requires external setup (Pub/Sub), has ongoing effects until stopped, or what changes trigger notifications. This leaves critical operational details unspecified.

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. It's front-loaded and appropriately sized for the tool's complexity, though it may be too brief given the lack of other context.

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 (real-time monitoring with 3 parameters), no annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects, usage context, or integration details, leaving significant gaps for an AI agent to understand how to invoke it correctly.

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 parameters are fully documented in the schema. The description adds no meaning beyond the schema—it doesn't explain how 'topicName' integrates with Pub/Sub, what 'labelIds' represent, or the implication of 'labelFilterAction'. Baseline 3 is appropriate as the schema does 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 'Watch for changes to the user's mailbox' clearly states the action (watch) and resource (mailbox), but it's vague about what 'watch' entails (e.g., real-time monitoring, notifications) and doesn't distinguish it from siblings like 'stop_mail_watch' or list operations. It provides a basic purpose 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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., setting up Cloud Pub/Sub), when to choose it over polling tools like 'list_messages', or how it relates to 'stop_mail_watch'. The description offers no usage context or exclusions.

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