No user-submitted related servers found.
Scored across 1 tool
With only one tool, there is no possibility of selection confusion. The tool's purpose—retrieving posts from a public Facebook Page—is stated clearly and cannot be mistaken for anything else.
The single name get_facebook_page_posts follows a clean verb_noun pattern (get + resource) and is fully descriptive of what it returns. There are no competing conventions to clash with.
One tool is defensible for a narrowly scoped scraper whose only job is fetching page posts, but it is on the thin side—there is no way to fetch post-level detail or paginate through a broader workflow. It sits at the borderline of 'focused' and 'underbuilt'.
The response shape is rich (date, text, reactions, comments, shares, media, link), covering the core read operation. However, there is no visible surface for pagination/date-range control, per-post detail, or bulk retrieval, so agents needing more than a single default fetch will hit a dead end.