Skip to main content
Glama

Manage Event

manage_event
Destructive

Create, update, delete, and RSVP to Google Calendar events. Manage event details like attendees, reminders, and recurrence.

Instructions

Manages calendar events. Supports creating, updating, deleting, and RSVP.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYesThe user's Google email address. Required.
actionYesAction to perform - "create", "update", "delete", or "rsvp".
summaryNoEvent title (required for create).
start_timeNoStart time in RFC3339 format (required for create).
end_timeNoEnd time in RFC3339 format (required for create).
event_idNoEvent ID (required for update and delete).
calendar_idNoCalendar ID (default: 'primary').primary
descriptionNoEvent description.
locationNoEvent location.
attendeesNoAttendee email addresses or objects.
timezoneNoTimezone (e.g., "America/New_York").
attachmentsNoList of Google Drive file URLs or IDs to attach.
add_google_meetNoWhether to add/remove Google Meet.
remindersNoCustom reminder objects.
use_default_remindersNoWhether to use default reminders.
transparencyNo"opaque" (busy) or "transparent" (free).
visibilityNo"default", "public", "private", or "confidential".
color_idNoEvent color ID (1-11, update only).
recurrenceNoRFC5545 recurrence rules for a recurring event, e.g. ["RRULE:FREQ=WEEKLY;COUNT=10"].
guests_can_modifyNoWhether attendees can modify.
guests_can_invite_othersNoWhether attendees can invite others.
guests_can_see_other_guestsNoWhether attendees can see other guests.
responseNoRSVP response — "accepted", "declined", "tentative", or "needsAction" (rsvp action only).
rsvp_commentNoOptional message to include with the RSVP response (rsvp action only).
send_updatesNoNotification behavior for create, update, delete, and rsvp — "all" (default), "externalOnly", or "none".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Annotations already indicate destructive behavior (destructiveHint=true) and non-read-only. The description adds only the action list, with no extra context about deletion permanence, permission needs, or rate limits. Minimal added value beyond annotations.

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 a single sentence with a clean list of actions. It is front-loaded and efficient, though it could slightly expand on usage without becoming verbose.

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 complex tool with 25 parameters, multiple actions, and an output schema, the description is too minimal. It omits per-action parameter requirements, return information, and constraints like the 'user_google_email' being required. Inadequate for full context.

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 100%, so the schema already documents all 25 parameters. The description adds no further parameter meaning or relationships (e.g., required params per action). 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 manages calendar events and lists the specific actions: creating, updating, deleting, and RSVP. This provides a specific verb+resource and distinguishes it from sibling tools like 'get_events' (read-only).

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?

The description lists supported actions but lacks explicit when-to-use guidance or alternatives. It implies use for mutations on events, but no mention of when to use other tools like 'get_events' or constraints. Adequate but could be improved.

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/chadvdwww-hash/worksuite-mcp'

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