Facebook Posts Scraper MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token, but a call requires one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_facebook_page_postsA | Get posts from public Facebook Pages. Returns one row per post with date, text, reactions, comments, shares, media type, and link. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.