team_members_update

Update one or more team members (bulk): set their team role, their consumption cap, or both. Requires a team admin (OAuth) or a team-scoped API key with the team.members.manage scope; other credentials get a permission error. Setting max_consumption additionally requires a real team admin: a team.members.manage API key can change roles but not caps (the API refuses it per member). Args: - team_id: required - member_ids: required, 1-32 member user IDs (from team_members_list) - role: optional, 'admin' or 'member', applied to every listed member - max_consumption: optional, consumption cap in Creative Units (CU) over the current billing period, applied to every listed member. Use a value >= 0 to cap, -1 for unlimited, or null to clear the per-member override and fall back to the team-wide default. - response_format: optional, 'json' (default) or 'markdown' Provide at least one of role or max_consumption. Returns: per-member outcome rows (updated | failed | skipped). Demoting the last admin fails server-side. API keys are refused: a key's role is a scope list, and its cap is managed in the Scenario portal. Processes members one by one and reports a per-member outcome. If the response has status "partial", call the tool again with the "remaining" list to finish. Don't use when: Changing project roles, use project_members_update. Setting caps on an API key, manage that in the Scenario portal.