events/get-event reads one event completely: both time representations, the timezone it belongs to, the all-day and multiday flags, cost, the resolved venue and organizers, and its categories.
It also reports whether the event is recurring — the one fact you need before deciding whether this suite can edit it.
At a glance
| Ability | events/get-event |
| Toolset | The Events Calendar — toolset/events-calendar |
| Group | The Events Calendar › Events |
| Requires | The Events Calendar, active on the site |
| Capability | manage_options |
| Safety | Read-only — changes nothing |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Abilities Manager 0.0.34 and later |
How it works
The interesting part of an event is its time, and time here has three parts that must agree: the local strings a human reads, the UTC strings everything else sorts by, and the Olson timezone that relates them. This returns all three, so nothing downstream has to guess which one it is holding.
The derived flags come back too. All day is not “starts at 00:00” — it is a stored property that changes how the calendar renders the event. Multiday is computed against the event’s own timezone, which is not always the same answer you get computing it against the site’s.
Venue and organizers arrive as records, not IDs. An event stores only the IDs, and a dangling one is possible — a venue can be trashed while events still point at it — so resolving here means a broken link shows up as a missing record rather than as a number that looks fine.
If the event recurs, the response says so. events/update-event refuses those, and knowing before you try is better than a refusal after.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
id | integer | Yes | The event ID. |
What comes back
| Name | Type | What it is |
|---|---|---|
event | object | Title, status, content, local and UTC start and end, timezone and abbreviation, all-day and multiday flags, cost, featured flag, external URL, venue, organizers, categories and the recurring flag. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Show me everything about event 1840.
It resolves to one call:
{
"ability": "events/get-event",
"parameters": {
"id": 1840
}
}Worth knowing
- Read this before
events/update-eventwhen you intend to change dates. The timezone you get back is the one your new times will be interpreted in. - A recurring event can be read here perfectly well. It just cannot be written.
- The cost is the display string, not a number. Sites use
Free,$25–$40and similar, and the calendar stores exactly what was typed.
Related abilities
- Update Event — change it once you have read it
- List Events — find the event first
- Get Venue — the venue in full
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category