Skip to main content
Glama

update_event

Update an existing calendar event by ID, changing only the provided details like time, title, or invitees. For recurring events, edit one occurrence or the whole series.

Instructions

Update an existing calendar event.

Use create_event for new events. Only specified fields are changed. For recurring events, pass an occurrence ID (from search_events) to modify just that single occurrence, or the master ID to change the whole series.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the event to update, as returned by search_events.
fromNoEmail address to organize from when adding the first participants. Must match one of the account's own addresses. Has no effect when the event already has an organizer.
colorNoSix-digit hex color. Pass an empty string to clear it and inherit from the calendar.
startNoStart date-time in ISO 8601 format (e.g. "2026-03-15T14:00:00").
titleNoEvent title.
durationNoDuration in ISO 8601 format, e.g. "PT1H" or "P1D".
isAllDayNoSet true to convert this into a true all-day (date-only, floating) event, or false to convert one back into a timed event.
locationNoLocation name or address. Pass an empty string to clear.
timeZoneNoIANA time zone. Ignored for all-day events.
recurrenceNoRecurrence rules, same shape as create_event's recurrence. Only meaningful on a series master.
descriptionNoEvent description or notes. Pass an empty string to clear.
addParticipantsNoInvitees to add, e.g. [{"name": "Jo", "email": "jo@example.com"}]. Duplicates against existing invitees are skipped. SENDS REAL INVITATION EMAILS.
removeParticipantsNoInvitees to uninvite, by email or display name. Matching is case-insensitive; a name matching more than one invitee is an error, so pass the email to disambiguate. The organizer is never removed. SENDS REAL CANCELLATIONS.
Behavior4/5

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

The description discloses that only specified fields are changed, giving transparency about its mutation behavior. It does not explicitly mention potential side effects like sending invitation emails, but that is detailed in parameter descriptions; given no annotations, the description provides reasonable transparency.

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 concise, using two sentences to convey the core function and key usage instructions without unnecessary detail.

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?

The description covers the essential context: update existing, create for new, only specified fields, and recurring event handling. It does not discuss output or errors, but given the simple update operation and no output schema, it is sufficiently complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds value to the id parameter by clarifying that a recurrence ID targets a single occurrence while the master ID affects the whole series, enhancing understanding beyond the schema's basic description.

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 updates an existing calendar event, and distinguishes it from create_event for new events, making the purpose unambiguous.

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?

It provides explicit guidance on when to use this tool (update) versus create_event, and explains how to handle recurring events by specifying occurrence vs master ID, covering the main usage scenarios.

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/duanefields/calendar-mcp'

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