swarmtix_teams_list

Lists the teams in this connection's organisation that the authorizing organizer belongs to, in alphabetical order by name, one page at a time. Each entry carries the team's id and name, the account that administers it, and the role this organizer holds in it.

When you would reach for it

• To see which teams the connection can act through.
• To check your own role in a team before trying something an editor can do and a viewer cannot.
• To find a team's administrator when you need someone to grant access.

Scope

organization:read

Organisation-level reference data. It is not your billing, payout or account settings — no scope covers those.

Parameters

The organisation and the organizer come from the access token. There is no parameter for either.

Example call

{
  "name": "swarmtix_teams_list",
  "arguments": {}
}

What comes back

[
  {
    "id": "6a3f9c12-8e47-4d05-b7a2-1c93f5e08d64",
    "name": "Conference Crew",
    "administratorUserId": "1d7f4b90-2c85-4e63-a018-9b5d6f2a3c47",
    "yourRole": "EventCreator"
  },
  {
    "id": "b0e52d71-4a96-4c38-81fd-7e3b0c62a495",
    "name": "Front of House",
    "administratorUserId": "cf1908ad-6e24-4b37-95c0-8d2a41e6f073",
    "yourRole": "Analytics"
  }
]

Teams come back alphabetically by name, with the id as a tiebreak.

What happens when you call it

1. limit is checked.
2. The teams this organizer belongs to are fetched.
3. The organisation filter is applied here, at this step, rather than by the service. The service takes an organisation id and does not use it — its query filters on team membership alone — so an organizer who belongs to teams in two organisations would otherwise get both organisations' teams back from a token issued for one. The returned rows also carry no organisation of their own, so the ids are taken back to the database to find out which organisation each team is really in, and anything outside this connection's organisation is dropped.
4. Duplicates are collapsed. A member holding two roles on one team appears twice in the source data; the first is kept.
5. The list is sorted by name, one page is cut, and the result is serialized.

Troubleshooting

A team you know exists is missing

Two possibilities, in this order:

• The authorizing organizer is not a member of it. This tool lists teams you belong to.
• The team belongs to a different organisation. A connection covers one organisation; swarmtix_whoami names it.

The list is empty

The organizer account on this connection belongs to no teams inside this organisation. That is normal for a sole organiser — teams are how access is shared with other people.

yourRole is not what you expected

The role is the one the organizer holds in that team, not an organisation-wide role. A person can be an event creator in one team and read-only in another.

"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 organization:read. Reconnect and grant it to use this tool."

Reconnect and approve organization:read.

"Swarmtix could not complete this request. Nothing was changed."

The team fetch failed. Retry; if it persists, quote the time to support.

Use cases

• Access questions — "who can edit this event's team?"
• Explaining a refusal — a read-only role explains why an event will not open for editing
• Finding the administrator to ask for a permission change
• Onboarding check after someone has been added to a team