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

Manage Focus Time

manage_focus_time

Destructive

Create, list, update, or delete Focus Time events on Google Calendar to auto-decline meetings and set Do Not Disturb for 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

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 "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.
`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. 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.

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.9/5.0

Behavior4/5

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

Annotations indicate destructiveHint=true and idempotentHint=false, which the description supports by mentioning update/delete actions. It adds context about auto-declining invitations and Do Not Disturb status, which is valuable. However, it doesn't disclose details like whether updates are irreversible or what happens to existing settings when updated, but the annotations cover the safety profile adequately.

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 description is a single sentence that is informative but concise. It front-loads the purpose and key behaviors. No fluff, and each clause adds value—purpose, auto-decline feature, and chat status default. Could argue it's slightly dense, but efficient.

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?

Given the tool's complexity (16 params, multiple actions), the description is complete enough for agents to understand the tool's core purpose and behavior. The output schema likely covers return values. However, it could benefit from explicit notes on action-specific usage, but the schema covers that. No critical gaps.

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 coverage is 100%, with every parameter well-documented (e.g., timezone requirements, date formats, action-specific fields). The description adds no extra parameter semantics beyond what the schema provides. Since the schema fully covers parameter meaning, baseline 3 is appropriate.

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 clearly states the tool manages Focus Time events on Google Calendar, and explains their special behavior (auto-declining meetings, Do Not Disturb status). It distinguishes itself from sibling calendar tools like get_events and manage_event by focusing on this specific event type. The purpose is unambiguous and specific.

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?

While the description explains what Focus Time events are, it doesn't explicitly guide when to use this tool versus alternatives like manage_event or manage_out_of_office. There's no clear 'when to use' vs 'when not to use' guidance. The description implies usage for creating focus time blocks, but does not name alternatives or edge cases.

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

Deploy Server