Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Manage Out of Office

manage_out_of_office

Destructive

Manage out-of-office events on Google Calendar: create, list, update, or delete them to auto-decline meeting invitations and set your availability status.

Instructions

Manages Out of Office events on Google Calendar. These special events auto-decline meeting invitations and set the user's status to "Out of office" across Google Workspace.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`action`	Yes	Action to perform - "create", "list", "update", or "delete".
`summary`	No	Display text on the calendar. Defaults to "Out of Office".
`end_time`	No	End date/time (exclusive). Same format as start_time. For a single full day on April 5, use start_time='2026-04-05' and end_time='2026-04-06'. Required for create.
`event_id`	No	Event ID. Required for "update" and "delete" actions.
`time_max`	No	For "list" action: end of time range.
`time_min`	No	For "list" action: start of time range. Defaults to current time. Recurring series are expanded into individual instances in the requested range.
`timezone`	No	Timezone for the event (e.g., "America/New_York", "Europe/London"). Required when using date-only values or dateTime values without an explicit UTC offset.
`recurrence`	No	RFC5545 recurrence rules for a recurring Out of Office series, e.g. ["RRULE:FREQ=WEEKLY;COUNT=10"].
`start_time`	No	Start date/time. Use 'YYYY-MM-DD' for full-day or RFC3339 for partial-day (e.g., '2024-04-05T09:00:00Z'). Date-only values are auto-converted to dateTime (midnight-to-midnight). Required for create.
`calendar_id`	No	Calendar ID. Defaults to 'primary'. Out of Office status events live on primary calendars, so use 'primary' or a user's primary calendar ID/email rather than a secondary calendar ID.	primary
`max_results`	No	For "list" action: maximum events to return. Defaults to 10.
`decline_message`	No	Message included when auto-declining invitations.
`auto_decline_mode`	No	How to handle conflicting invitations. One of: "declineAllConflictingInvitations" (default), "declineOnlyNewConflictingInvitations", "declineNone".
`user_google_email`	Yes	The user's Google email address. Required.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedv1.28.0Sep 24, 2026

removedInput schema / properties / auto_decline_mode / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / auto_decline_mode / type
```
Added value: +"string"
```

removedInput schema / properties / decline_message / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / decline_message / type
```
Added value: +"string"
```

removedInput schema / properties / end_time / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / end_time / type
```
Added value: +"string"
```

removedInput schema / properties / event_id / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / event_id / type
```
Added value: +"string"
```

removedInput schema / properties / recurrence / anyOf

Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / recurrence / items
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / recurrence / type
```
Added value: +"array"
```

removedInput schema / properties / start_time / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / start_time / type
```
Added value: +"string"
```

removedInput schema / properties / summary / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / summary / type
```
Added value: +"string"
```

removedInput schema / properties / time_max / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / time_max / type
```
Added value: +"string"
```

removedInput schema / properties / time_min / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / time_min / type
```
Added value: +"string"
```

removedInput schema / properties / timezone / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / timezone / type
```
Added value: +"string"
```

Addedv1.0.1Jul 31, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The description adds a concrete behavioral detail (auto-declining invitations and setting status) beyond what annotations state. Annotations already flag destructive and non-read-only, but the description gives a specific side effect. It does not cover all behaviors (e.g., effects of deletion) but adds meaningful context.

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?

Two sentences, both informative. The first states the action and resource, the second explains the unique purpose. No filler or redundancy. It is concise and front-loaded, though it could arguably include a brief mention of supported actions.

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

Completeness3/5

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

The tool is complex with 14 parameters and multiple actions, but the schema documents every parameter and its role. The description provides a high-level overview but does not mention the action variants (create, list, update, delete) or required fields; however, the schema covers these. It is adequate but could be more complete with a sentence about supported operations.

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 schema has 100% description coverage for all 14 parameters, so the description is not required to explain parameters. The description does not add any parameter-specific information, which is acceptable given the schema's completeness. Baseline 3 applies.

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 states a specific verb (manages) and resource (Out of Office events on Google Calendar), and explains the special behavior (auto-decline, status change). It clearly identifies what the tool does but does not explicitly differentiate from sibling tools like manage_event or manage_focus_time, so it falls short of a perfect 5.

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 given on when to use this tool versus alternatives. It does not mention that it is specific to Out of Office events or that regular events should use manage_event, nor does it provide any exclusions or conditions.

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

Deploy Server