Skip to main content
Glama

manage_event

Create, update, delete, or RSVP to Google Calendar events with full control over attendees, reminders, recurrence, and visibility settings.

Instructions

Create, update, delete, or RSVP to a calendar event.

Side effects: mutates calendar state on the account. Delete is destructive. Attendee email notifications follow send_updates. For read-only fetches use get_events; for focus-time blocks use manage_focus_time. Requires the calendar.events OAuth scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address (authenticated account).
actionYes"create", "update", "delete", or "rsvp". Case-insensitive.
summaryNoEvent title. Required for create; optional for update.
start_timeNoRFC3339 start, e.g. "2026-05-01T15:00:00-04:00" or "2026-05-01" for all-day. Required for create.
end_timeNoRFC3339 end (exclusive). Required for create.
event_idNoEvent ID from get_events. Required for update, delete, rsvp.
calendar_idNoCalendar ID from list_calendars, or "primary".primary
descriptionNoEvent body text. Supports plain text and some HTML.
locationNoFree-form location string or address.
attendeesNoList of emails (e.g. ["alice@ex.com"]) or attendee objects (e.g. [{"email": "alice@ex.com", "optional": true}]).
timezoneNoIANA zone like "America/New_York". Applied to start/end when they are tz-naive.
attachmentsNoDrive file IDs or sharable URLs — attached as event files visible to attendees.
add_google_meetNoTrue to attach a Meet conference, False on update to remove it.
remindersNoList of reminder objects like [{"method": "popup", "minutes": 10}] or a JSON string of same. Ignored when use_default_reminders=True.
use_default_remindersNoTrue (default on create) to use the calendar's default reminders. Set False to use `reminders`.
transparencyNo"opaque" shows as busy; "transparent" shows as free.
visibilityNo"default", "public", "private", or "confidential".
color_idNoColor index 1-11 (update only); see Calendar color map.
recurrenceNoRFC5545 rules, e.g. ["RRULE:FREQ=WEEKLY;BYDAY=MO,WE;COUNT=10"].
guests_can_modifyNoAllow attendees to edit the event.
guests_can_invite_othersNoAllow attendees to invite more people.
guests_can_see_other_guestsNoAllow attendees to see the guest list.
responseNoRSVP value for action="rsvp" — "accepted", "declined", "tentative", or "needsAction".
rsvp_commentNoOptional note sent with the RSVP.
send_updatesNoRSVP notification behavior — "all" (default), "externalOnly", or "none".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully carries the burden, disclosing side effects ('mutates calendar state', 'Delete is destructive'), attendee notifications, and required scope. This is comprehensive for safe agent usage.

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?

The description is three sentences, front-loaded with core purpose, followed by side effects and alternatives. Every sentence earns its place with no waste.

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

Completeness5/5

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

Given 25 parameters, an output schema, and no annotations, the description provides essential context: purpose, side effects, alternatives, and required scope. It is complete for safe and effective usage.

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 the schema already documents all parameters. The description adds no additional parameter-specific semantics beyond the action types. 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's purpose: 'Create, update, delete, or RSVP to a calendar event.' It uses a specific verb and resource, and distinguishes itself from siblings like get_events and manage_focus_time.

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

Usage Guidelines5/5

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

The description explicitly provides when to use this tool vs alternatives: 'For read-only fetches use get_events; for focus-time blocks use manage_focus_time.' It also mentions side effects and required OAuth scope.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/HuntsDesk/ve-gws'

If you have feedback or need assistance with the MCP directory API, please join our Discord server