calendar__update_event
Access
Requires a project integration connection for calendar.
Call type: Can change resources.
Arguments
Example request
Send this JSON-RPC request through an initialized MCP client. Replace sample identifiers and values before calling the tool. See MCP client setup.
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "calendar__update_event",
"arguments": {
"calendarId": "example",
"eventId": "example"
}
}
}Result
No output schema is published for this tool. The input contract does not define its return fields. Inspect the MCP response content and isError; do not assume a fixed object shape. See the calendar integration reference for provider setup and tool context.
Full schemas
{
"type": "object",
"properties": {
"calendarId": {
"type": "string",
"description": "Calendar ID"
},
"eventId": {
"type": "string",
"description": "Event ID to update"
},
"sendUpdates": {
"type": "string",
"description": "Whether to send update notifications: all, externalOnly, or none"
},
"summary": {
"type": "string",
"description": "Updated event title"
},
"description": {
"type": "string",
"description": "Updated event description"
},
"start": {
"type": "object",
"description": "Event time: {dateTime: \"YYYY-MM-DDTHH:mm:ss\", timeZone: \"IANA zone\"} for local time. Explicit-offset timestamps retain provider semantics; use date for all-day events."
},
"end": {
"type": "object",
"description": "Event time: {dateTime: \"YYYY-MM-DDTHH:mm:ss\", timeZone: \"IANA zone\"} for local time. Explicit-offset timestamps retain provider semantics; use date for all-day events."
},
"attendees": {
"type": "array",
"description": "Updated array of {email: string} attendees"
},
"location": {
"type": "string",
"description": "Updated event location"
}
},
"required": [
"calendarId",
"eventId"
],
"description": "Arguments for the calendar__update_event tool."
}