Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

gmail.users.settings.updateVacation

Configure or disable a Gmail vacation responder by updating auto-reply settings such as subject, message body, schedule, and contact/domain restrictions. Returns the updated VacationSettings as JSON.

Instructions

Updates vacation responder settings. For more information, see Manage vacation settings with the Gmail API [HTTP PUT] — updates the resource; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON VacationSettings object accepting enableAutoReply, endTime, responseBodyHtml, responseBodyPlainText, responseSubject, restrictToContacts, restrictToDomain, startTime; pass it via params or whole via body_file Siblings over the same resource: getAutoForwarding, getImap, getLanguage, getPop, getVacation, updateAutoForwarding, updateImap, updateLanguage, updatePop.

Input Schema

NameRequiredDescriptionDefault
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
userIdYes[URL path segment] User's email address. The special value "me" can be used to indicate the authenticated user.me
dry_runNoReturn the request that would be sent, without sending it.
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON VacationSettings object.
request_bodyNoRequest body of type VacationSettings: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

NameRequiredDescriptionDefault
endTimeNo
startTimeNo
enableAutoReplyNo
responseSubjectNo
responseBodyHtmlNo
restrictToDomainNo
restrictToContactsNo
responseBodyPlainTextNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / body_file / description
      Previous value: -"Read the request body from this file ('-' for stdin) instead of building one from the parameters."New value: +"Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON VacationSettings object."
    • addedInput schema / properties / request_body
      Added value: +{
+  "description": "Request body of type VacationSettings: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "enableAutoReply": {
+      "type": "boolean"
+    },
+    "endTime": {
+      "type": "string"
+    },
+    "responseBodyHtml": {
+      "type": "string"
+    },
+    "responseBodyPlainText": {
+      "type": "string"
+    },
+    "responseSubject": {
+      "type": "string"
+    },
+    "restrictToContacts": {
+      "type": "boolean"
+    },
+    "restrictToDomain": {
+      "type": "boolean"
+    },
+    "startTime": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / userId / default
      Added value: +"me"
    • changedInput schema / properties / userId / description
      Previous value: -"User's email address. The special value \"me\" can be used to indicate the authenticated user."New value: +"[URL path segment] User's email address. The special value \"me\" can be used to indicate the authenticated user."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "enableAutoReply": {
+      "type": "boolean"
+    },
+    "endTime": {
+      "type": "string"
+    },
+    "responseBodyHtml": {
+      "type": "string"
+    },
+    "responseBodyPlainText": {
+      "type": "string"
+    },
+    "responseSubject": {
+      "type": "string"
+    },
+    "restrictToContacts": {
+      "type": "boolean"
+    },
+    "restrictToDomain": {
+      "type": "boolean"
+    },
+    "startTime": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does reasonably well: it discloses HTTP PUT semantics, that the operation is refused when a readonly safety profile is active, and that the API response resource is returned as JSON. It does not state required body fields or permission requirements, but it gives more than the bare minimum 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is stated first, followed by useful details. It is a single dense paragraph, and the trailing list of nine sibling tools is somewhat verbose, but the overall text is not bloated and every clause is at least tangentially relevant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is not strictly required, yet the description covers write semantics, safety-profile behavior, request body shape, and body transport. It lacks detail on required body fields and permissions, but is sufficient for an agent to call the tool 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 the schema already documents every parameter. The description merely enumerates the VacationSettings body fields and repeats the transport options (params vs body_file) already present in the schema's request_body and body_file descriptions, adding little semantic value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

The description opens with a specific verb and resource: 'Updates vacation responder settings.' It also names the sibling read counterpart (getVacation) and the other settings update tools, so an agent can distinguish this write operation from lookups without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states that the call is refused under '--readonly safety profiles', which is a useful usage constraint. However, it never explicitly says when to choose this tool over getVacation or the other update* siblings; the sibling list provides context but no explicit decision guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools