Skip to main content
Glama

update_vacation

Configure Gmail vacation responder settings to automatically send replies during absences, including start/end times, message content, and recipient restrictions.

Instructions

Update vacation responder settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enableAutoReplyYesWhether the vacation responder is enabled
responseSubjectNoOptional subject line for the vacation responder auto-reply
responseBodyPlainTextYesResponse body in plain text format
restrictToContactsNoWhether responses are only sent to contacts
restrictToDomainNoWhether responses are only sent to users in the same domain
startTimeNoStart time for sending auto-replies (epoch ms)
endTimeNoEnd time for sending auto-replies (epoch ms)

Implementation Reference

  • src/index.ts:929-946 (registration)
    Registration of the 'update_vacation' MCP tool, defining input schema with Zod and the handler function that uses handleTool to call Gmail API's updateVacation method.
    server.tool("update_vacation",
      "Update vacation responder settings",
      {
        enableAutoReply: z.boolean().describe("Whether the vacation responder is enabled"),
        responseSubject: z.string().optional().describe("Optional subject line for the vacation responder auto-reply"),
        responseBodyPlainText: z.string().describe("Response body in plain text format"),
        restrictToContacts: z.boolean().optional().describe("Whether responses are only sent to contacts"),
        restrictToDomain: z.boolean().optional().describe("Whether responses are only sent to users in the same domain"),
        startTime: z.string().optional().describe("Start time for sending auto-replies (epoch ms)"),
        endTime: z.string().optional().describe("End time for sending auto-replies (epoch ms)")
      },
      async (params) => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.settings.updateVacation({ userId: 'me', requestBody: params })
          return formatResponse(data)
        })
      }
    )
  • Handler function for 'update_vacation' tool that executes the Gmail API call to update vacation settings.
    async (params) => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.settings.updateVacation({ userId: 'me', requestBody: params })
        return formatResponse(data)
      })
  • Zod schema defining input parameters for the 'update_vacation' tool.
    {
      enableAutoReply: z.boolean().describe("Whether the vacation responder is enabled"),
      responseSubject: z.string().optional().describe("Optional subject line for the vacation responder auto-reply"),
      responseBodyPlainText: z.string().describe("Response body in plain text format"),
      restrictToContacts: z.boolean().optional().describe("Whether responses are only sent to contacts"),
      restrictToDomain: z.boolean().optional().describe("Whether responses are only sent to users in the same domain"),
      startTime: z.string().optional().describe("Start time for sending auto-replies (epoch ms)"),
      endTime: z.string().optional().describe("End time for sending auto-replies (epoch ms)")
  • Shared helper function used by 'update_vacation' handler (and others) 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'update' which implies a mutation, but doesn't disclose critical behavioral traits such as required permissions (e.g., admin access), whether changes are reversible, potential side effects (e.g., sending auto-replies immediately), or error conditions (e.g., invalid time formats). This leaves significant gaps for a mutation tool.

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 action ('update') and resource, making it easy to parse quickly. Every word earns its place by conveying the essential purpose.

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 complexity of a mutation tool with 7 parameters and no annotations or output schema, the description is incomplete. It lacks behavioral context (e.g., safety, side effects), usage guidance, and any mention of return values or errors. While the schema covers parameters well, the overall tool understanding remains inadequate for safe and effective use.

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 each parameter clearly documented (e.g., 'enableAutoReply' as 'Whether the vacation responder is enabled'). The description adds no additional meaning beyond this, as it doesn't explain parameter interactions, defaults, or usage examples. With high schema coverage, the baseline score of 3 is appropriate.

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 'Update vacation responder settings' clearly indicates the verb ('update') and resource ('vacation responder settings'), which is better than a tautology. However, it doesn't specify what exactly gets updated (e.g., enabling/disabling, configuring response content, setting time windows) or differentiate from the sibling 'get_vacation' tool, making it somewhat vague.

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 to retrieve current settings first with 'get_vacation'), exclusions, or comparisons with other tools like 'update_auto_forwarding' for related email settings.

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