Skip to main content
Glama
nabheet

google-services-mcp

by nabheet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create calendar event

google_calendar_create_event

Create timed or all-day events in Google Calendar with title, start/end, attendees, reminders, recurrence, and account options.

Instructions

Create a timed or all-day event. All-day events use YYYY-MM-DD dates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYesEnd: RFC3339 datetime or YYYY-MM-DD (exclusive) for all-day.
startYesStart: RFC3339 datetime or YYYY-MM-DD for all-day.
accountNoAccount nickname to use.
colorIdNoEvent color ID (1-11).
summaryYesEvent title.
locationNo
timeZoneNoIANA time zone, e.g. America/Denver. Required for recurring timed events.
attendeesNoAttendee emails.
calendarIdNoCalendar ID (default primary).
recurrenceNoRRULE strings, e.g. ["RRULE:FREQ=WEEKLY;BYDAY=TH"].
descriptionNo
sendUpdatesNoControl attendee notification emails.
transparencyNoShow as busy (opaque) or free (transparent).
reminderMethodNoReminder delivery method.
reminderMinutesNoMinutes before event.
remindersUseDefaultNoUse calendar default reminders instead of overrides.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.1.60
    • addedInput schema / properties / colorId
      Added value: +{
+  "description": "Event color ID (1-11).",
+  "type": "string"
+}
    • addedInput schema / properties / recurrence
      Added value: +{
+  "description": "RRULE strings, e.g. [\"RRULE:FREQ=WEEKLY;BYDAY=TH\"].",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / reminderMethod
      Added value: +{
+  "description": "Reminder delivery method.",
+  "enum": [
+    "email",
+    "popup"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / reminderMinutes
      Added value: +{
+  "description": "Minutes before event.",
+  "exclusiveMinimum": 0,
+  "maximum": 9007199254740991,
+  "type": "integer"
+}
    • addedInput schema / properties / remindersUseDefault
      Added value: +{
+  "description": "Use calendar default reminders instead of overrides.",
+  "type": "boolean"
+}
    • addedInput schema / properties / sendUpdates
      Added value: +{
+  "description": "Control attendee notification emails.",
+  "enum": [
+    "all",
+    "externalOnly",
+    "none"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / timeZone
      Added value: +{
+  "description": "IANA time zone, e.g. America/Denver. Required for recurring timed events.",
+  "type": "string"
+}
    • addedInput schema / properties / transparency
      Added value: +{
+  "description": "Show as busy (opaque) or free (transparent).",
+  "enum": [
+    "opaque",
+    "transparent"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changedv0.1.30
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / attendees / items / pattern
      Added value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  3. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and falls well short. For a mutation tool it says nothing about attendee invite emails, sendUpdates defaults, reminder behavior, or required auth/scopes. The one useful nugget is the all-day date convention, but that duplicates the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, no filler, and the primary purpose is front-loaded ahead of the format note. Every sentence earns its place, even if the total content is thin.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter mutation tool with no annotations and no output schema, a two-sentence description is inadequate. Aspects like attendee notification control, recurrence/timezone interaction, and default behavior are left entirely to the schema, leaving meaningful gaps for correct invocation.

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 88%, so the schema already documents nearly all 16 parameters, giving a baseline of 3. The description's only parameter-related content (all-day YYYY-MM-DD dates) merely restates what the start/end schema descriptions already say, adding no new semantics.

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 ('Create a ... event') and distinguishes two modes (timed vs all-day). It does not differentiate itself from nearby siblings such as google_calendar_create, google_calendar_update_event, or google_calendar_create_meet, so an agent gets the core action but no explicit routing signal.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives like google_calendar_create or google_calendar_create_meet. The only guidance offered is a date-format note for all-day events, which is a formatting rule rather than usage direction.

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