Skip to main content
Glama

update_vacation

Configure Gmail vacation responder settings to automatically reply to emails during absences. Set start/end times, customize messages, and control who receives responses.

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

  • Handler function that executes the update_vacation tool by calling Gmail API's users.settings.updateVacation with the provided parameters.
    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 the input parameters for the update_vacation tool, including enableAutoReply, responseBodyPlainText, and optional fields like startTime and endTime.
    {
      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)")
    },
  • src/index.ts:943-960 (registration)
    Registration of the update_vacation tool on the MCP server, including description, input schema, and handler function.
    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)
        })
      }
    )
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 but offers minimal information. 'Update' implies a mutation operation, but the description doesn't specify required permissions, whether changes are immediate or scheduled, what happens to existing settings not mentioned, or error conditions. For a tool that modifies user email settings, this is a significant transparency gap.

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 that states the core purpose without unnecessary words. It's appropriately sized for what it communicates and front-loads the essential information.

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 7 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns, error conditions, side effects, or how it interacts with other email settings. The agent would need to guess about the operation's behavior and outcomes based on minimal 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 7 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.

Purpose4/5

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

The description clearly states the action ('update') and resource ('vacation responder settings'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'get_vacation' or explain how it differs from other update tools like 'update_auto_forwarding' or 'update_label'.

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 (like needing to first retrieve current settings with 'get_vacation'), no comparison with sibling tools, and no indication of when this operation is appropriate versus other vacation-related actions.

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

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