grr

Overview Schema Source Related Servers Discussions Admin

calendar.calendarList.insert

Adds an existing Google Calendar to the user's calendar list, making that calendar available in their calendar view.

Instructions

Inserts an existing calendar into the user's calendar list [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 CalendarListEntry object accepting accessRole, autoAcceptInvitations, backgroundColor, colorId, conferenceProperties, dataOwner, defaultReminders, deleted and 13 more fields; pass it via params or whole via body_file Siblings over the same resource: delete, get, list, patch, update, watch.

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 CalendarListEntry object.
`request_body`	No	Request body of type CalendarListEntry: pass it via `params` (merged into the built body) or whole via `body_file`.
`colorRgbFormat`	No	[query parameter] Whether to use the foregroundColor and backgroundColor fields to write the calendar colors (RGB). If this feature is used, the index-based colorId field will be

Output Schema

Name	Required	Description	Default
`id`	No
`etag`	No
`kind`	No
`hidden`	No
`colorId`	No
`deleted`	No
`primary`	No
`summary`	No
`location`	No
`selected`	No
`timeZone`	No
`dataOwner`	No
`accessRole`	No
`description`	No
`backgroundColor`	No
`foregroundColor`	No
`summaryOverride`	No
`defaultReminders`	No
`conferenceProperties`	No
`notificationSettings`	No
`autoAcceptInvitations`	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 CalendarListEntry object."

addedInput schema / properties / request_body

Added value: +{
+  "description": "Request body of type CalendarListEntry: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "accessRole": {
+      "type": "string"
+    },
+    "autoAcceptInvitations": {
+      "type": "boolean"
+    },
+    "backgroundColor": {
+      "type": "string"
+    },
+    "colorId": {
+      "type": "string"
+    },
+    "conferenceProperties": {
+      "properties": {
+        "allowedConferenceSolutionTypes": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "dataOwner": {
+      "type": "string"
+    },
+    "defaultReminders": {
+      "items": {
+        "properties": {
+          "method": {
+            "type": "string"
+          },
+          "minutes": {
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "deleted": {
+      "type": "boolean"
+    },
+    "description": {
+      "type": "string"
+    },
+    "etag": {
+      "type": "string"
+    },
+    "foregroundColor": {
+      "type": "string"
+    },
+    "hidden": {
+      "type": "boolean"
+    },
+    "id": {
+      "type": "string"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "location": {
+      "type": "string"
+    },
+    "notificationSettings": {
+      "properties": {
+        "notifications": {
+          "items": {
+            "properties": {
+              "method": {
+                "type": "string"
+              },
+              "type": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "primary": {
+      "type": "boolean"
+    },
+    "selected": {
+      "type": "boolean"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "summaryOverride": {
+      "type": "string"
+    },
+    "timeZone": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / colorRgbFormat / description

Previous value: -"Whether to use the foregroundColor and backgroundColor fields to write the calendar colors (RGB). If this feature is used, the index-based colorId field will be"New value: +"[query parameter] Whether to use the foregroundColor and backgroundColor fields to write the calendar colors (RGB). If this feature is used, the index-based colorId field will be"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "accessRole": {
+      "type": "string"
+    },
+    "autoAcceptInvitations": {
+      "type": "boolean"
+    },
+    "backgroundColor": {
+      "type": "string"
+    },
+    "colorId": {
+      "type": "string"
+    },
+    "conferenceProperties": {
+      "properties": {
+        "allowedConferenceSolutionTypes": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "dataOwner": {
+      "type": "string"
+    },
+    "defaultReminders": {
+      "items": {
+        "properties": {
+          "method": {
+            "type": "string"
+          },
+          "minutes": {
+            "type": "integer"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "deleted": {
+      "type": "boolean"
+    },
+    "description": {
+      "type": "string"
+    },
+    "etag": {
+      "type": "string"
+    },
+    "foregroundColor": {
+      "type": "string"
+    },
+    "hidden": {
+      "type": "boolean"
+    },
+    "id": {
+      "type": "string"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "location": {
+      "type": "string"
+    },
+    "notificationSettings": {
+      "properties": {
+        "notifications": {
+          "items": {
+            "properties": {
+              "method": {
+                "type": "string"
+              },
+              "type": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "primary": {
+      "type": "boolean"
+    },
+    "selected": {
+      "type": "boolean"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "summaryOverride": {
+      "type": "string"
+    },
+    "timeZone": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it flags the operation as a mutation ('creates or triggers a change'), discloses it is 'refused under --readonly safety profiles,' and states it returns the API response resource as JSON. It doesn't cover idempotency or duplicate-entry behavior, keeping it short of 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-loaded with the core action and safety constraint before the field list and siblings. The enumeration of body fields ('...and 13 more fields') is somewhat wasteful given full schema coverage, but overall the structure is efficient and readable.

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 mutation tool with nested body objects, the description covers the mutation semantics, safety-profile behavior, and body-passing options; return values needn't be explained since an output schema exists. Missing only edge-case behavior (duplicates, idempotency) for a full 5.

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%, so parameters are already documented. The description enumerates some body fields and explains the 'params' vs 'body_file' passing mechanism, but this largely restates schema content, so the baseline 3 applies.

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+resource: 'Inserts an existing calendar into the user's calendar list.' It explicitly names the sibling operations (delete, get, list, patch, update, watch) over the same resource, so an agent can place it precisely in the CRUD family.

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?

Names the siblings but provides no explicit when-to-use / when-not-to-use guidance distinguishing insert from patch or update (which mutate the same list entry). Usage is only implied by 'Inserts an existing calendar,' leaving the insert-vs-update decision 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