list_teams
ManagementList Teams
List all teams available to the authenticated user. Call this first before tools that need team_id or project_id. Args: - response_format: optional — 'json' (default) or 'markdown' Returns: the teams the user can access, usually with nested project summaries. If multiple teams or projects are available, ask the user which one to use before continuing. Examples: - "What team IDs can I use?" -> call list_teams first - "I need a team before running a model" -> call list_teams, then confirm the team/project with the user Don't use when: You already have a confirmed team_id and only need its projects. Prefer list_projects instead.
read-onlyidempotentopen-world
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| response_format | enum(json | markdown) | json | Output format: 'json' for structured data, 'markdown' for human-readable text. |
Example Request
JSON
{}Example Response
JSON
{
"teams": [
{
"id": "team_abc123",
"name": "Acme Studio",
"projects": [
{
"id": "proj_xyz789",
"name": "Fantasy RPG"
}
]
}
]
}Common Use Cases
- Discover team IDs at the start of a session before calling project-scoped tools
- Identify when multiple teams are available so the agent can ask the user to choose