Facebook Scraper3 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | 不适用 (Not applicable) | |
| PORT | No | 不适用 (Not applicable) | |
| API_KEY | Yes | API 密钥 (API Key for Facebook Scraper3 API) |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| profiles_photosB | Read profiles photos (from recent) Use cursor to get next page of results |
| comment_by_idC | Get comment by comment id |
| search_peopleD | Searches people |
| search_hashtagC | Search posts with hashtag |
| profile_reelsB | Get profile reels. Get |
| page_eventsB | Get all future events created by page |
| post_reactionsC | Get post reactions |
| commentsC | Get nested comments. You need to use legacy fb id |
| page_reelsC | Get page reels by page id - use reels_page_id now |
| listing_detailsC | Get listing details |
| searchC | Search marketplace. Use cursor to get next page |
| comments_2B | Get post comments. Use comment_id from post |
| search_groups_postsD | Searches group for posts |
| page_videosC | Get page videos by page delegate id. YOU NEED TO USE DELEGATE ID, NOT PAGE ID. |
| pages_photosB | Read page photos (from recent) Use cursor to get next page of results |
| pages_postsB | Read page posts (from recent) |
| page_detailsC | Read page details |
| page_past_eventsA | Get all past events created by page. Use cursor to get next page of results. |
| get_group_postsA | Get group posts. Only PUBLIC groups can be scrapped! If there are no post response, check if group is not private. |
| get_group_future_eventsA | Get group future events. Only PUBLIC groups can be scrapped! If there are no post response, check if group is not private. Use cursor to get next page of events! |
| search_eventsC | Searches for facebook events |
| game_livesB | Get game live videos Use cursor to get next page. |
| browse_gamesA | Browse games. Use empty query for browse all games. Use cursor to get next page. |
| page_reviewsB | Get page reviews. Use cursor to get next page |
| search_videoC | Performs facebook videos search |
| profile_postsC | Read profile posts (from recent), if public |
| events_details_by_idC | Get events details by event id |
| locationsB | Search for facebook locations id. If you get strange results, try add country to query and/or try without diacritic |
| search_postC | Performs facebook posts search |
| events_details_by_urlC | Get events details |
| profiles_details_by_idC | Get profiles details by id |
| profile_details_by_urlC | Get profile details by url |
| profile_idB | Get profile id by url |
| get_post_detailsB | Get post details by url or post id. If both are set, post id is used. |
| get_group_detailsC | Get group summary |
| get_group_idC | Getting group facebook id |
| page_idB | get page id from url |
| resharesB | Get post reshares |
| search_placeC | Search for fb place |
| search_pagesB | Searches for facebook pages |
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 40 tools
The tool set has clear distinctions for major categories like pages, groups, profiles, and search, but there is significant overlap within categories that could cause confusion. For example, 'comments' and 'comments_2' have ambiguous boundaries, and multiple search tools (e.g., 'search_post', 'search_video', 'search_hashtag') might be misselected due to similar purposes. Descriptions help clarify some differences, but the overlap is notable.
Most tools follow a consistent verb_noun or noun_verb pattern with underscores, such as 'browse_games', 'get_group_details', and 'search_events'. There are minor deviations like 'page_id' (noun_noun) and 'reshares' (noun only), but overall the naming is predictable and readable across the set.
With 40 tools, the count is excessive for a scraper server, leading to potential bloat and complexity. While Facebook has many data types, this many tools suggests over-fragmentation rather than a well-scoped set, making it harder for agents to navigate efficiently. A more consolidated approach with 15-25 tools would be more appropriate.
The tool surface covers a wide range of Facebook entities comprehensively, including pages, groups, profiles, events, posts, comments, and various search functions. Minor gaps exist, such as limited update or delete operations (expected for scraping), but agents can perform most data retrieval tasks without significant dead ends in the core workflows.