Lists an event's scheduled dates with their ids, capacities and local and UTC times

swarmtix_event_dates_list

Lists the scheduled dates of one event, earliest first, one page at a time. Each entry carries the date's id, its start and end in both local and UTC form, its capacity, and whether it is still active.

When you would reach for it

To get a date id. This is the only tool that returns one, and four other tools take it: swarmtix_orders_list, swarmtix_attendees_list, swarmtix_attendees_search, swarmtix_analytics_event and swarmtix_tickets_summary.
To read a schedule with its UTC values, when local times in a report would be ambiguous.
To check per-date capacity on a multi-day run.

Scope

events:read

Parameters

Name	Type	Required	Default	Description
`event`	string	Yes	—	The event's id (a GUID) or its URL slug.
`limit`	integer	No	`50`	How many dates to return. 1 to 200.
`cursor`	string	No	—	The cursor from the end of a previous page. Omit to start at the beginning.

Example call

{
  "name": "swarmtix_event_dates_list",
  "arguments": { "event": "spring-summit-2026" }
}

What comes back

[
  {
    "id": "2c9a7f31-4d88-4f6a-b0e1-5a7c3d9e2f41",
    "eventId": "8f14e45f-ceea-467a-9c3d-1b2a5f6e7d80",
    "start": "2026-11-04T19:00:00",
    "end": "2026-11-04T23:00:00",
    "startUtc": "2026-11-04T19:00:00Z",
    "endUtc": "2026-11-04T23:00:00Z",
    "capacity": 250,
    "active": true,
    "partOfMultiDaySelection": true
  },
  {
    "id": "5b81de04-3f6c-4a92-84d7-9e0b1a7c2f53",
    "eventId": "8f14e45f-ceea-467a-9c3d-1b2a5f6e7d80",
    "start": "2026-11-05T10:00:00",
    "end": "2026-11-05T17:00:00",
    "startUtc": "2026-11-05T10:00:00Z",
    "endUtc": "2026-11-05T17:00:00Z",
    "capacity": 200,
    "active": true,
    "partOfMultiDaySelection": true
  }
]

Field	What it is
`id`	The date's id — what the other tools take as `eventDate`
`eventId`	The event it belongs to, echoed so a row stands alone
`start`, `end`	Local start and end, in the event's own timezone
`startUtc`, `endUtc`	The same instants in UTC
`capacity`	How many people this date can take
`active`	Whether the date is still part of the schedule
`partOfMultiDaySelection`	Whether the date is one leg of a multi-day run rather than a standalone occurrence

Dates come back earliest first. Two dates starting at the same instant are broken apart by id, so the order is the same on every call and a cursor lands in the same place.

The event's timezone is on swarmtix_events_get as timezone. Read it before presenting a local time to anybody.

What happens when you call it

The event identifier is resolved and the ownership checks run before anything else touches the event.
limit is checked. Out of range is refused, not clamped.
Every active date of the event is fetched in one unbounded list.
The list is re-sorted by start time and then by id. The underlying query sorts by start alone, which is not a total order; the id tiebreak is what makes the cursor trustworthy.
One page is cut, projected to the fields above, and serialized. If the JSON would breach the response budget, trailing rows are dropped and the cursor is taken from the last row actually sent.

Troubleshooting

"Event not found, or this connection does not have access to it."

The event does not exist, or it belongs to a different organisation than this connection covers. The two are deliberately indistinguishable. Check the slug against swarmtix_events_list.

The list is empty

The event has no dates yet. A freshly created draft has none — swarmtix_events_create makes an event with a name and nothing else, and swarmtix_event_dates_set is what gives it a schedule.

"`cursor` is not valid: the date it points at is no longer in this list."

The cursor was genuine but the date it named has gone from the schedule between the two calls. Start the list again.

"`limit` is not valid: it was 0. Expected a whole number from 1 to 200, or nothing for 50."

limit must be at least 1.

"This connection is not authorized for `events:read`. Reconnect and grant it to use this tool."

Reconnect and approve events:read.

Use cases

Narrowing a report to one day of a multi-day event
Checking a schedule after swarmtix_event_dates_set ran
Reconciling timezones — the UTC pair removes the ambiguity local times carry
Capacity planning — per-date capacity against per-date sales from swarmtix_tickets_summary

swarmtix_event_dates_list

On this page