Skip to main content
Glama

calendar.events.watch

Create a notification channel to monitor changes to calendar events and receive webhook updates; returns the Channel resource with address, expiration, and token details.

Instructions

Watch for changes to Events 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, import, insert, instances, list, move, patch, quickAdd, update.

Input Schema

NameRequiredDescriptionDefault
qNo[query parameter] Free text search terms to find events that match these terms in the following fields: - summary - description - location - attendee's displayName - attendee's e
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
dry_runNoReturn the request that would be sent, without sending it.
iCalUIDNo[query parameter] Specifies an event ID in the iCalendar format to be provided in the response. Optional. Use this if you want to search for an event by its iCalendar ID.
orderByNo[query parameter] The order of the events returned in the result. Optional. The default is an unspecified, stable order. Values: `startTime` = Order by the start date/time (ascending). This is only available when querying single events (i.e. the parameter singleEvents is True); `updated` = Order by last modification time (ascending)..
timeMaxNo[query parameter] Upper bound (exclusive) for an event's start time to filter by. Optional. The default is not to filter by start time. Must be an RFC3339 timestamp with mandator
timeMinNo[query parameter] Lower bound (exclusive) for an event's end time to filter by. Optional. The default is not to filter by end time. Must be an RFC3339 timestamp with mandatory ti
timeZoneNo[query parameter] Time zone used in the response. Optional. The default is the time zone of the calendar.
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON Channel object.
pageTokenNo[query parameter] Token specifying which result page to return. Optional.
syncTokenNo[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
calendarIdYes[URL path segment] Calendar identifier. To retrieve calendar IDs call the calendarList.list method. If you want to access the primary calendar of the currently logged in user, use
eventTypesNo
maxResultsNo[query parameter] Maximum number of events returned on one result page. The number of events in the resulting page may be less than this value, or none at all, even if there are 250
updatedMinNo[query parameter] Lower bound for an event's last modification time (as a RFC3339 timestamp) to filter by. When specified, entries deleted since this time will always be included
showDeletedNo[query parameter] Whether to include deleted events (with status equals "cancelled") in the result. Cancelled instances of recurring events (but not the underlying recurring even
maxAttendeesNo[query parameter] The maximum number of attendees to include in the response. If there are more than the specified number of attendees, only the participant is returned. Optional
request_bodyNoRequest body of type Channel: pass it via `params` (merged into the built body) or whole via `body_file`.
singleEventsNo[query parameter] Whether to expand recurring events into instances and only return single one-off events and instances of recurring events, but not the underlying recurring even
alwaysIncludeEmailNo[query parameter] Deprecated and ignored.
showHiddenInvitationsNo[query parameter] Whether to include hidden invitations in the result. Optional. The default is False.
sharedExtendedPropertyNo
privateExtendedPropertyNo

Output Schema

NameRequiredDescriptionDefault
idNo
kindNo
typeNo
tokenNo
paramsNo
addressNo
payloadNo
expirationNo
resourceIdNo
resourceUriNo

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 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"
      +}
  2. Changed28 schema fields changed
    • changedInput schema / properties / alwaysIncludeEmail / description
      Previous value: -"Deprecated and ignored."New value: +"[query parameter] Deprecated and ignored."
    • changedInput schema / properties / calendarId / description
      Previous value: -"Calendar identifier. To retrieve calendar IDs call the calendarList.list method. If you want to access the primary calendar of the currently logged in user, use"New value: +"[URL path segment] Calendar identifier. To retrieve calendar IDs call the calendarList.list method. If you want to access the primary calendar of the currently logged in user, use"
    • changedInput schema / properties / eventTypes / items / description
      Previous value: -"Event types to return. Optional. This parameter can be repeated multiple times to return events of different types. If unset, returns all event types."New value: +"[query parameter] Event types to return. Optional. This parameter can be repeated multiple times to return events of different types. If unset, returns all event types. Values: `birthday` = Special all-day events with an annual recurrence.; `default` = Regular events.; `focusTime` = Focus time events.; `fromGmail` = Events from Gmail.; `outOfOffice` = Out of office events.; `workingLocation` = Working location events.."
    • changedInput schema / properties / iCalUID / description
      Previous value: -"Specifies an event ID in the iCalendar format to be provided in the response. Optional. Use this if you want to search for an event by its iCalendar ID."New value: +"[query parameter] Specifies an event ID in the iCalendar format to be provided in the response. Optional. Use this if you want to search for an event by its iCalendar ID."
    • changedInput schema / properties / maxAttendees / description
      Previous value: -"The maximum number of attendees to include in the response. If there are more than the specified number of attendees, only the participant is returned. Optional"New value: +"[query parameter] The maximum number of attendees to include in the response. If there are more than the specified number of attendees, only the participant is returned. Optional"
    • addedInput schema / properties / maxAttendees / format
      Added value: +"int32"
    • addedInput schema / properties / maxAttendees / minimum
      Added value: +1
    • addedInput schema / properties / maxResults / default
      Added value: +"250"
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of events returned on one result page. The number of events in the resulting page may be less than this value, or none at all, even if there are "New value: +"[query parameter] Maximum number of events returned on one result page. The number of events in the resulting page may be less than this value, or none at all, even if there are "
    • addedInput schema / properties / maxResults / format
      Added value: +"int32"
    • addedInput schema / properties / maxResults / minimum
      Added value: +1
    • changedInput schema / properties / orderBy / description
      Previous value: -"The order of the events returned in the result. Optional. The default is an unspecified, stable order."New value: +"[query parameter] The order of the events returned in the result. Optional. The default is an unspecified, stable order. Values: `startTime` = Order by the start date/time (ascending). This is only available when querying single events (i.e. the parameter singleEvents is True); `updated` = Order by last modification time (ascending).."
    • 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 / privateExtendedProperty / items / description
      Previous value: -"Extended properties constraint specified as propertyName=value. Matches only private properties. This parameter might be repeated multiple times to return event"New value: +"[query parameter] Extended properties constraint specified as propertyName=value. Matches only private properties. This parameter might be repeated multiple times to return event"
    • changedInput schema / properties / q / description
      Previous value: -"Free text search terms to find events that match these terms in the following fields: - summary - description - location - attendee's displayName - attendee's e"New value: +"[query parameter] Free text search terms to find events that match these terms in the following fields: - summary - description - location - attendee's displayName - attendee's e"
    • changedInput schema / properties / sharedExtendedProperty / items / description
      Previous value: -"Extended properties constraint specified as propertyName=value. Matches only shared properties. This parameter might be repeated multiple times to return events"New value: +"[query parameter] Extended properties constraint specified as propertyName=value. Matches only shared properties. This parameter might be repeated multiple times to return events"
    • changedInput schema / properties / showDeleted / description
      Previous value: -"Whether to include deleted events (with status equals \"cancelled\") in the result. Cancelled instances of recurring events (but not the underlying recurring even"New value: +"[query parameter] Whether to include deleted events (with status equals \"cancelled\") in the result. Cancelled instances of recurring events (but not the underlying recurring even"
    • changedInput schema / properties / showHiddenInvitations / description
      Previous value: -"Whether to include hidden invitations in the result. Optional. The default is False."New value: +"[query parameter] Whether to include hidden invitations in the result. Optional. The default is False."
    • changedInput schema / properties / singleEvents / description
      Previous value: -"Whether to expand recurring events into instances and only return single one-off events and instances of recurring events, but not the underlying recurring even"New value: +"[query parameter] Whether to expand recurring events into instances and only return single one-off events and instances of recurring events, but not the underlying recurring even"
    • 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"
    • changedInput schema / properties / timeMax / description
      Previous value: -"Upper bound (exclusive) for an event's start time to filter by. Optional. The default is not to filter by start time. Must be an RFC3339 timestamp with mandator"New value: +"[query parameter] Upper bound (exclusive) for an event's start time to filter by. Optional. The default is not to filter by start time. Must be an RFC3339 timestamp with mandator"
    • addedInput schema / properties / timeMax / format
      Added value: +"date-time"
    • changedInput schema / properties / timeMin / description
      Previous value: -"Lower bound (exclusive) for an event's end time to filter by. Optional. The default is not to filter by end time. Must be an RFC3339 timestamp with mandatory ti"New value: +"[query parameter] Lower bound (exclusive) for an event's end time to filter by. Optional. The default is not to filter by end time. Must be an RFC3339 timestamp with mandatory ti"
    • addedInput schema / properties / timeMin / format
      Added value: +"date-time"
    • changedInput schema / properties / timeZone / description
      Previous value: -"Time zone used in the response. Optional. The default is the time zone of the calendar."New value: +"[query parameter] Time zone used in the response. Optional. The default is the time zone of the calendar."
    • changedInput schema / properties / updatedMin / description
      Previous value: -"Lower bound for an event's last modification time (as a RFC3339 timestamp) to filter by. When specified, entries deleted since this time will always be included"New value: +"[query parameter] Lower bound for an event's last modification time (as a RFC3339 timestamp) to filter by. When specified, entries deleted since this time will always be included"
    • addedInput schema / properties / updatedMin / format
      Added value: +"date-time"
    • 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"
      +}
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral load and does well: it discloses that this is a mutating POST, that it is refused under readonly profiles, that it returns the API response as JSON, and that the body is a Channel object passed via params or body_file. It omits details such as authentication requirements, channel expiration, or rate limits, but the core behavior is clear.

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 front-loaded with the core action and safety behavior, then moves into body and sibling context. It is dense but appropriately sized for a 24-parameter tool with a nested request body, though the sibling list and parenthetical details could be structured more cleanly.

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 complexity of a watch operation with 24 parameters, a nested Channel body, and no annotations, the description covers the essential action, safety refusal, return format, and body-passing mechanisms. The schema and output schema carry the remaining detail, so the description is largely complete for an agent to invoke 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 88%, so the parameters are already well documented in the schema. The description adds a little by explaining that the request body is a Channel object and can be supplied through `params` or `body_file`, but it does not add meaning beyond the schema for the many query parameters.

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 and resource: 'Watch for changes to Events resources' and clarifies that it is an HTTP POST that creates or triggers a change. It names sibling event tools but does not explain the conditions that distinguish watch from list, get, or instances, so it falls short of full sibling differentiation.

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?

Usage is implied by 'Watch for changes' and the safety-profile note that it is 'refused under --readonly safety profiles.' However, there is no explicit guidance on when to choose this tool over calendar.events.list or other sibling event tools, nor are prerequisites or exclusions described.

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