team_members_list
ManagementcatalogList Team Members
Not in the default tool list
This tool lives in the tool catalog. Discover it with scenario_tools_search (or enumerate everything with scenario_tools_list) and run it via scenario_tool_execute_read. To list every tool directly, connect with ?toolsets=full.
List a team's members and pending invitations.
Args:
- team_id: required — team to list members for
- response_format: optional — 'json' (default) or 'markdown'
Returns: members ({id, email, role, created_at}) and pending_invitations ({email, role, status, created_at}). Roles are 'admin' or 'member'. For a team admin (OAuth) only, each member also carries their consumption cap and spend this billing period (unlimited, max_consumption, consumption, remaining, cap_source 'override'|'team_default'|'none'; max_consumption and remaining null when unlimited), plus period {start, end} with the reset date. Other callers, API keys included, never see these fields. API keys are separate from members — use api_keys_list / api_key_get / api_key_update / api_key_delete (project scope). Keys are created in the Scenario portal.
Examples:
- "Who is on my team?" -> team_members_list with the confirmed team_id
- "Show pending invites" -> team_members_list, read pending_invitations
- "How much has each member spent against their cap?" -> team_members_list as a team admin
Don't use when: You need project-level roles. Use project_members_list instead.
read-onlyidempotentopen-world
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| team_id | string | ✓ | Team ID. Get it from teams_list. |
| project_id | string | — | Tenant context for OAuth sessions only. |
| response_format | enum(json | markdown) | json | Output format: 'json' for structured data, 'markdown' for human-readable text. |