grr

Overview Schema Source Related Servers Discussions Admin

calendar.calendarList.watch

Watch CalendarList resources for changes by creating a notification channel; use it to trigger updates when users add, remove, or modify calendars.

Instructions

Watch for changes to CalendarList resources [HTTP POST] — creates or triggers a change; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON Channel object accepting address, expiration, id, kind, params, payload, resourceId, resourceUri and 2 more fields; pass it via params or whole via body_file Siblings over the same resource: delete, get, insert, list, patch, update.

Input Schema

Name	Required	Description
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`params`	No	Parameter map merged into the request; typed parameters win.
`dry_run`	No	Return the request that would be sent, without sending it.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON Channel object.
`pageToken`	No	[query parameter] Token specifying which result page to return. Optional.
`syncToken`	No	[query parameter] Token obtained from the nextSyncToken field returned on the last page of results from the previous list request. It makes the result of this list request contai
`maxResults`	No	[query parameter] Maximum number of entries returned on one result page. By default the value is 100 entries. The page size can never be larger than 250 entries. Optional.
`showHidden`	No	[query parameter] Whether to show hidden entries. Optional. The default is False.
`showDeleted`	No	[query parameter] Whether to include deleted calendar list entries in the result. Optional. The default is False.
`request_body`	No	Request body of type Channel: pass it via `params` (merged into the built body) or whole via `body_file`.
`minAccessRole`	No	[query parameter] The minimum access role for the user in the returned entries. Optional. The default is no restriction. Values: `freeBusyReader` = The user can read free/busy information.; `owner` = The user can read and modify events and access control lists.; `reader` = The user can read events that are not private.; `writer` = The user can read and modify events.; `writerWithoutPrivateAccess` = The user can read and modify events that aren't private. The user can read free/busy information about private events. The user can't modify private events..
`showOwnOrganizationOnly`	No	[query parameter] Whether to show only entries for calendars from the organization. This parameter is only applicable to Google Workspace users. Optional. The default is False.

Output Schema

Name	Required	Description	Default
`id`	No
`kind`	No
`type`	No
`token`	No
`params`	No
`address`	No
`payload`	No
`expiration`	No
`resourceId`	No
`resourceUri`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

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 Channel object."

addedInput schema / properties / request_body

Added value: +{
+  "description": "Request body of type Channel: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "address": {
+      "type": "string"
+    },
+    "expiration": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "params": {
+      "type": "object"
+    },
+    "payload": {
+      "type": "boolean"
+    },
+    "resourceId": {
+      "type": "string"
+    },
+    "resourceUri": {
+      "type": "string"
+    },
+    "token": {
+      "type": "string"
+    },
+    "type": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed10 schema fields changedOct 26, 2026

changedInput schema / properties / maxResults / description

Previous value: -"Maximum number of entries returned on one result page. By default the value is 100 entries. The page size can never be larger than 250 entries. Optional."New value: +"[query parameter] Maximum number of entries returned on one result page. By default the value is 100 entries. The page size can never be larger than 250 entries. Optional."

addedInput schema / properties / maxResults / format
```
Added value: +"int32"
```
addedInput schema / properties / maxResults / minimum
```
Added value: +1
```

changedInput schema / properties / minAccessRole / description

Previous value: -"The minimum access role for the user in the returned entries. Optional. The default is no restriction."New value: +"[query parameter] The minimum access role for the user in the returned entries. Optional. The default is no restriction. Values: `freeBusyReader` = The user can read free/busy information.; `owner` = The user can read and modify events and access control lists.; `reader` = The user can read events that are not private.; `writer` = The user can read and modify events.; `writerWithoutPrivateAccess` = The user can read and modify events that aren't private. The user can read free/busy information about private events. The user can't modify private events.."

changedInput schema / properties / pageToken / description

Previous value: -"Token specifying which result page to return. Optional."New value: +"[query parameter] Token specifying which result page to return. Optional."

changedInput schema / properties / showDeleted / description

Previous value: -"Whether to include deleted calendar list entries in the result. Optional. The default is False."New value: +"[query parameter] Whether to include deleted calendar list entries in the result. Optional. The default is False."

changedInput schema / properties / showHidden / description

Previous value: -"Whether to show hidden entries. Optional. The default is False."New value: +"[query parameter] Whether to show hidden entries. Optional. The default is False."

changedInput schema / properties / showOwnOrganizationOnly / description

Previous value: -"Whether to show only entries for calendars from the organization. This parameter is only applicable to Google Workspace users. Optional. The default is False."New value: +"[query parameter] Whether to show only entries for calendars from the organization. This parameter is only applicable to Google Workspace users. Optional. The default is False."

changedInput schema / properties / syncToken / description

Previous value: -"Token obtained from the nextSyncToken field returned on the last page of results from the previous list request. It makes the result of this list request contai"New value: +"[query parameter] Token obtained from the nextSyncToken field returned on the last page of results from the previous list request. It makes the result of this list request contai"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "address": {
+      "type": "string"
+    },
+    "expiration": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "params": {
+      "type": "object"
+    },
+    "payload": {
+      "type": "boolean"
+    },
+    "resourceId": {
+      "type": "string"
+    },
+    "resourceUri": {
+      "type": "string"
+    },
+    "token": {
+      "type": "string"
+    },
+    "type": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the load and does most of it: it discloses the POST semantics, that the call creates/triggers a change (side effect), that it is blocked under readonly profiles, and the shape and delivery of the response. Missing only channel lifecycle/renewal and permission requirements, which keeps it below a 5.

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?

Front-loads the verb/resource and the safety restriction, then body mechanics, then siblings — a sensible order with no filler sentences. It is a dense single paragraph with an appended sibling list, slightly reducing scannability but nothing is wasteful.

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?

For a 12-parameter mutation tool with no annotations, it covers operation type, side effects, safety gating, body delivery, and return behavior, and an output schema exists to cover response details. Only the webhook channel lifecycle (id/address/expiration expectations) is left implied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description adds value by explaining how the body is supplied — merged field-wise via `params` or wholesale via `body_file` — and notes the Channel object's field set. The enumerated body fields largely restate the nested schema, capping it at 4.

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?

States a specific verb and resource ('Watch for changes to CalendarList resources'), plus the HTTP verb, and explicitly enumerates the sibling operations on the same resource (delete, get, insert, list, patch, update). An agent can differentiate this webhook-registration call from a plain list/get without inspecting 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?

Gives one implicit when-not ('refused under --readonly safety profiles'), which is genuinely useful for gating. However, it never says when to prefer watch over polling calendarList.list or how it relates to the sibling list it names, leaving the choice between the listed siblings to inference.

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

Deploy Server