Hi we’re running into a similar issue with a similar use case for this particular endpoint/feature. I see that something similar has been brought up before.
I think possibly even adding a roles attribute to the /api/v2/organizations/{id}/members would be super helpful. The current work around is to request member roles for each member which isn’t scalable as member sizes begin to grow.