events/list-venues returns the venues on the site, newest first, each with its full address and contact details.
This is almost always the call before creating or rescheduling an event, because an event stores a venue ID and nothing else.
At a glance
| Ability | events/list-venues |
| Toolset | The Events Calendar — toolset/events-calendar |
| Group | The Events Calendar › Venues |
| 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
A venue in The Events Calendar is its own post type, with the address broken into separate fields — street, city, state, postcode, country, phone, website. The event does not copy any of it; it stores the venue ID, and everything displayed on the event page is read through that link at render time.
Which is why finding the right ID matters more than it sounds. Sites accumulate near-duplicate venues — the same room entered three times with slightly different spellings — and picking the wrong one produces an event that looks correct and sends people to the wrong place.
The search filter runs over the name, so you can narrow before you choose. The full address comes back on every row precisely so that near-duplicates can be told apart without a second call each.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
search | string | No | Free-text search over the name. |
page | integer | No — defaults to 1 | 1-based page number. |
per_page | integer | No — defaults to 20 | Results per page, capped at 100. |
What comes back
| Name | Type | What it is |
|---|---|---|
venues | array | One entry per venue: ID, name, status, address, city, state, postcode, country, phone and website. |
total | integer | Total venues, before paging. |
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:
What venues do we have on file, and which ones are in Bristol?
It resolves to one call:
{
"ability": "events/list-venues",
"parameters": {
"search": "Bristol",
"per_page": 50
}
}Worth knowing
- Newest first. The venue somebody just added is on the first page.
- Address fields are all optional in the calendar, so any of them can be empty. A venue with nothing but a name is legal and common.
- Search covers the name only. Use the returned address fields to filter by city yourself.
Related abilities
- Get Venue — one venue in full
- Create Venue — add one that is not there yet
- List Events — filter events by the venue ID you found
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category