Currently the Spring Social Facebook API does not support this kind of call. But I can see how it'd be useful. The challenge here is with the fields parameter. There are many things you can ask for there and if those things are returned, where would they be placed? Would I need to create a domain object capable of holding almost any field that could be asked for (most would be blank/null unless they're asked for)? Or should each object have a Map property to carry the extra stuff? Or should it be even more clever and allow you, the developer, to provide your own domain type to contain the extra fields?
That last option is the one that sounds most appealing and I really should give it some more thought. Maybe it should work something like how the FqlOperations.query() method works with a result mapper to help populate the object.
Note that although you may be asking for page data, the operation in your example is actually a search operation (and thus could pull back stuff unrelated to pages). Therefore, the solution should treat it as a search operation. And maybe the search operation is flexible enough to return results in any type the developer wants using a result mapper. Again, more thought is due to this.
May I ask you to create an improvement issue at https://jira.springsource.org/browse/SOCIALFB to track this?
Spring Social Project Lead