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

Manage Focus Time

manage_focus_time

Destructive

Creates, lists, updates, or deletes Google Calendar Focus Time events that auto-decline conflicting meetings and set Chat to Do Not Disturb to protect uninterrupted work.

Instructions

Manages Focus Time events on Google Calendar. These special events auto-decline meeting invitations and, by default, set the user's chat status to Do Not Disturb, helping protect blocks of uninterrupted work time.

Input Schema

Name	Required	Description	Default
`action`	Yes	Action to perform - "create", "list", "update", or "delete".
`summary`	No	Display text on the calendar. Defaults to "Focus Time".
`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.
`page_token`	No	For "list" action: token for the next page, taken from a previous response. Also pass the response's Pagination time_min as time_min, even if omitted on the first call. Keep all other query parameters unchanged.
`recurrence`	No	RFC5545 recurrence rules for a recurring Focus Time 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'. Focus Time status events live on primary calendars, so use 'primary' or a user's primary calendar ID/email rather than a secondary calendar ID.	primary
`chat_status`	No	Google Chat status during the focus time. Supports "doNotDisturb" (default) and "available".
`description`	No	Event description. Useful for adding context about what the focus time is for.
`max_results`	No	For "list" action: maximum events to return in one page. 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

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.2.0Oct 24, 2026

changedInput schema / properties / max_results / description

Previous value: -"For \"list\" action: maximum events to return. Defaults to 10."New value: +"For \"list\" action: maximum events to return in one page. Defaults to 10."

addedInput schema / properties / page_token

Added value: +{
+  "default": null,
+  "description": "For \"list\" action: token for the next page, taken from a previous response. Also pass the response's Pagination time_min as time_min, even if omitted on the first call. Keep all other query parameters unchanged.",
+  "type": "string"
+}

Changed25 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 / chat_status / anyOf

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

addedInput schema / properties / chat_status / 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 / description / anyOf

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

addedInput schema / properties / description / 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

A3.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuine behavioral context beyond that: these events auto-decline conflicting invitations and default the user's chat status to Do Not Disturb — side effects on the user's calendar and Chat presence that no structured field announces. It stops short of warning what a delete action destroys.

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 tight sentences with zero filler, front-loaded on the resource and then its distinguishing behavior. For a 17-parameter, four-action, destructive tool it is on the thin side, but nothing is redundant or buried.

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?

An output schema exists, so return values needn't be explained. However, a destructive multi-action tool with 17 parameters deserves at least action-level framing and a pointer to manage_event for ordinary events, and neither is present. Adequate but with clear gaps for the tool's complexity.

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% across 17 parameters, so the schema carries the parameter burden and baseline is 3. The description adds only lightly, implying the defaults that auto_decline_mode and chat_status control ("by default, set the user's chat status to Do Not Disturb") and confirming auto-decline behavior, but gives no per-action parameter guidance.

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?

States a specific verb and resource ("Manages Focus Time events on Google Calendar") and immediately differentiates the resource from ordinary events by describing its special auto-decline and DND behavior. It never names the siblings it must be distinguished from (manage_event, manage_out_of_office), so an agent still has to infer that general events belong elsewhere.

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?

Explains what a Focus Time event is and why a user would want one, which implies the usage context. But it gives no when-to-use/when-not-to-use guidance relative to manage_event or manage_out_of_office, and it never mentions the create/list/update/delete action modes the tool actually exposes. Usage is inferred rather than stated.

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

Deploy Server