swarmtix_venues_list
Lists the saved venue seating layouts belonging to the authorizing organizer account
swarmtix_venues_list
Lists the saved venue seating layouts belonging to the authorizing organizer account, in alphabetical order by name, one page at a time. Each entry carries the layout's id and name, its floor plan image if it has one, when it was created, and whether a seating map has been drawn on it.
When you would reach for it
- To see which venue layouts already exist before drawing another one.
- To check whether a layout has a seat map on it yet, rather than just a name and a floor plan.
- Pre-event readiness on a reserved-seating event.
Scope
organization:read
This list is scoped to your account, not your organisation
Layouts saved by other accounts in the same organisation are not listed. That is a limit of what the data records, not a choice about what to show you: a venue layout carries the account that saved it and nothing else — there is no organisation on the row at all.
Narrowing to the account is the only reading that cannot leak. An organisation-wide list would mean guessing which layouts belong to the organisation, and a wrong guess there shows one customer's venue to another.
If a colleague's layout is missing, that is why. It is visible to them, and to the events they build with it.
Parameters
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
limit | integer | No | 50 | How many venue layouts to return. 1 to 200. |
cursor | string | No | — | The cursor from the end of a previous page. Omit to start at the beginning. |
The organizer account comes from the access token. There is no parameter for it.
Example call
{
"name": "swarmtix_venues_list",
"arguments": { "limit": 2 }
}What comes back
[
{
"id": "c48e1b06-9f23-4a7d-85b1-0e6c2d3f97a5",
"name": "Culturgest Grande Auditório",
"floorPlanImage": "https://swarmtixstorage.blob.core.windows.net/…/culturgest.png",
"createdAt": "2026-02-14T10:05:31",
"active": true,
"hasSeatingMap": true
},
{
"id": "7f2b4d90-18c6-4e53-a0b7-92d5e6c41f08",
"name": "Studio B",
"createdAt": "2026-06-02T16:48:07",
"active": true,
"hasSeatingMap": false
}
]| Field | What it is |
|---|---|
id | The layout's id |
name | The layout's name |
floorPlanImage | The uploaded floor plan, if one was added. Absent otherwise. |
createdAt | When the layout was saved |
active | Whether the layout is still in use |
hasSeatingMap | Whether seats have actually been drawn on it |
hasSeatingMap is a yes-or-no answer, not the map. The seats themselves are not returned — nothing on this surface needs them, and the layout data is edited in the seat map editor in the dashboard.
What happens when you call it
limitis checked.- Venue layouts owned by the organizer account on the token are fetched, sorted by name and then by id.
- Six named fields are projected in the database query itself, rather than through the mapping the rest of the application uses. That mapping parses the stored seat map as it builds each row, with no guard, so one malformed layout would fail the whole page. Nothing here needs the parsed seats — only whether any were saved.
- One page is cut and serialized.
Troubleshooting
A layout a colleague created is missing
Expected — see scoping. Venue layouts are listed for the authorizing organizer account only.
hasSeatingMap is false on a layout you have drawn seats on
No seat configuration is stored against that layout. Open it in the seat map editor in the dashboard and save it.
floorPlanImage is missing from a row
No floor plan image was uploaded for that layout. The layout still works; it just has no background picture.
The list is empty
The authorizing organizer account has saved no venue layouts. Layouts are created in the dashboard — the MCP catalog has no tool for making one.
"limit is not valid: it was 500. Expected a whole number from 1 to 200, or nothing for 50."
limit must be between 1 and 200.
"This connection is not authorized for organization:read. Reconnect and grant it to use this tool."
Reconnect and approve organization:read.
Use cases
- Avoiding a duplicate layout before drawing a new one
- Readiness check on a reserved-seating event — is the map actually drawn?
- Venue history — which rooms this account has configured, and when
- Cleanup — spotting layouts that were named but never mapped