Thats the whole point, REST facilitates and often encourages bad design.
I've always held a strict rule where The R in REST stands for Resource (which isn't true). There's a user, an Invitation (and not an invite action on user, nor a state:invited or invited_at on user). there's a Session. There's links that clients follow, and everything is as small as possible. I really don't see how REST encourages God objects.
GQL solves this problem elegantly by allowing you to specify the data that you need in a single request.
That is just one example, there are many many others that you can google if you are actually interested.
Fair point.
But I ask my question again, differently worded: how does Graphql solve this? Why does GraphQL solve "many requests" and why can't you solve or avoid this in REST.