Skip to main content
Glama

watch_mailbox

Monitor Gmail mailbox for new emails and changes, sending notifications to a specified Pub/Sub topic when updates occur.

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:1300-1313 (registration)
    Registration of the 'watch_mailbox' tool, including input schema and handler implementation. The handler uses the Gmail API's users.watch method to watch the mailbox for changes and publish notifications to a specified Cloud Pub/Sub topic.
    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 authenticates via handleTool and calls Gmail API users.watch to set up mailbox watching.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.watch({ userId: 'me', requestBody: params })
        return formatResponse(data)
      })
    }
Behavior2/5

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

With no annotations, the description carries full burden but lacks behavioral details. It doesn't specify that this likely sets up a notification system (implied by 'topicName'), requires Pub/Sub configuration, or may have ongoing effects until stopped. No rate limits, permissions, or output format are mentioned.

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 no wasted words. It's front-loaded with the core purpose, though it could benefit from additional context to improve clarity without sacrificing brevity.

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 tool with 3 parameters, no annotations, and no output schema, the description is incomplete. It doesn't cover the tool's behavior (e.g., it sets up a watch, returns a confirmation), interactions with 'stop_mail_watch', or error conditions, leaving significant gaps for the agent.

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 fully documents parameters. The description adds no meaning beyond the schema—it doesn't explain how 'topicName' relates to notifications or how label filtering works in practice. 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). It distinguishes from siblings like 'stop_mail_watch' but not from other read operations like 'list_messages'.

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 (e.g., 'list_messages' for one-time queries, 'stop_mail_watch' to end monitoring). It mentions no prerequisites or exclusions, leaving the agent to infer usage from the tool name alone.

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