List, inspect, create, and update event records

Use list_events for bounded summaries and get_event after the user selects an owned record. create_event requires an exact ISO instant, coordinates, timezone, and idempotency key; the event and its chart are private by default. update_event keeps the attached event chart aligned when time or location changes. Embedded chart data and internal condition payloads are excluded from responses, and no event deletion tool is registered.

Request and response shapes

Input shape

{ query?: string; limit?: number } | { eventId: string } | { idempotencyKey: string; title: string; kind: string; startsAt: string; latitude: number; longitude: number; timezone: string } | { eventId: string; patch: EventPatch }

Output shape

{ events: EventSummary[] } | { event: SafeEvent } | { event: SafeEvent; created: boolean }

Examples

Request example

{
  "idempotencyKey": "event-conference-2026-07-19",
  "title": "Conference opening",
  "kind": "event",
  "startsAt": "2026-07-19T18:00:00.000Z",
  "latitude": 39.7392,
  "longitude": -104.9903,
  "timezone": "America/Denver"
}

Response example

{
  "event": {
    "id": "mcp_event_example",
    "title": "Conference opening"
  },
  "created": true
}

Common validation errors

Event tools require events:read or events:write and ownership is checked server-side.
Participant person IDs must belong to the connected account.

List, inspect, create, and update event records

Request and response shapes

Input shape

{ query?: string; limit?: number } | { eventId: string } | { idempotencyKey: string; title: string; kind: string; startsAt: string; latitude: number; longitude: number; timezone: string } | { eventId: string; patch: EventPatch }

Output shape

{ events: EventSummary[] } | { event: SafeEvent } | { event: SafeEvent; created: boolean }

Examples

Request example

{
  "idempotencyKey": "event-conference-2026-07-19",
  "title": "Conference opening",
  "kind": "event",
  "startsAt": "2026-07-19T18:00:00.000Z",
  "latitude": 39.7392,
  "longitude": -104.9903,
  "timezone": "America/Denver"
}

Response example

{
  "event": {
    "id": "mcp_event_example",
    "title": "Conference opening"
  },
  "created": true
}

Common validation errors

Event tools require events:read or events:write and ownership is checked server-side.
Participant person IDs must belong to the connected account.

List, inspect, create, and update event records

Request and response shapes

Input shape

Output shape

Examples

Request example

Response example

Common validation errors

Related questions

List, inspect, create, and update event records

Request and response shapes

Input shape

Output shape

Examples

Request example

Response example

Common validation errors

Related questions