facebook_get_page_idLABSCO SUMMARY
The URL-to-id tools are what make this workable from a chat client, where what you have is a link somebody pasted.
Most of this surface takes an id, and nobody has ids — they have a link. Dedicated resolvers for page, group, post and Instagram profile URLs mean the first step of any real task is covered instead of being an exercise left to the caller. The breadth is the other notable thing: the Ad Library and Marketplace are separate products with separate shapes, and folding them in behind one key removes the usual work of finding and paying for a scraper per surface. Two things to weigh: everything is public data read through a third party, so coverage and freshness are that vendor's rather than Meta's, and the tools cap what they return per call — six videos, for instance — so a sweep is a pagination loop, not one request.
What it is
A social-data client covering Facebook and Instagram across most of their public surfaces: pages and groups with their posts and videos, individual posts with reactions and comment threads, keyword and location search, the Meta Ad Library, and Facebook Marketplace including vehicles and rentals.
What you get
- Identity resolution first: separate tools turn a page, group, post or Instagram profile URL into the id every other call takes, so a pasted link is a usable starting point.
- Facebook pages and groups with their details, posts, videos and reels, all paginated and filterable by time.
- Post-level depth: reactions, shares, media attachments, top-level comments and the replies under a specific comment.
- Search across pages, people, posts, videos and locations, with location search returning the UIDs that geo-filter the other searches.
- The Meta Ad Library: search ads by keyword or page, read an archived ad's creative, spend and impressions, and list the supported country codes.
- Marketplace as its own surface — listings, seller profiles with ratings and reviews, categories, city coordinates for location filters, and dedicated vehicle and rental searches.
- Instagram profiles with bio and follower counts, posts, reels, highlights and the stories inside them, plus reels found by audio id and posts found by location.
Requirements
SOCIALAPIS_API_KEY. Everything reaches public data through the vendor's service, so no Facebook or Instagram account of your own is connected.
Setup effort
One command plus a key — npm install -g @socialapis/mcp, then supply credentials
USE CASES
01
Turning a link somebody sent you into data
Resolve the page, group, post or profile URL to its id first, then read the details — the step every other tool depends on.
02
Reading how a post actually performed
Get reactions, comments and shares on the post, then walk into the comment threads and the replies underneath them.
03
Seeing what a competitor is running as ads
Search the Meta Ad Library by page or keyword, then open an archived ad for its creative, spend and impressions.
04
Pricing something on Marketplace
Search listings in a city — with the coordinates lookup supplying the location filter — and check the seller's ratings and reviews before acting on a price.
05
Following an Instagram account properly
Read the profile, then its posts, reels and highlights — including the stories inside a highlight, which the profile view does not expose.
06
Finding what is being posted about a place or a sound
Pull posts tagged at a location, or reels using a specific audio id — two angles that a keyword search will not reach.
47 tools
Listed in project docs. Your client may show a different list.
facebook_get_page_detailsfacebook_get_page_postsfacebook_get_page_videosfacebook_get_page_reelsfacebook_get_group_idfacebook_get_group_detailsfacebook_get_group_postsfacebook_get_group_videosfacebook_get_post_idfacebook_get_post_detailsfacebook_get_post_details_extendedfacebook_get_post_attachmentsfacebook_get_video_detailsfacebook_get_post_commentsfacebook_get_comment_repliesfacebook_search_pagesfacebook_search_peoplefacebook_search_locationsfacebook_search_postsfacebook_search_videosfacebook_ads_searchfacebook_ads_page_detailsfacebook_ads_archive_detailsfacebook_ads_keywordsfacebook_ads_countriesfacebook_marketplace_searchfacebook_marketplace_listingfacebook_marketplace_sellerfacebook_marketplace_categoriesfacebook_marketplace_city_coordinatesfacebook_marketplace_vehiclesfacebook_marketplace_rentalsfacebook_download_mediainstagram_get_user_idinstagram_get_profile_detailsinstagram_get_profile_postsinstagram_get_profile_reelsinstagram_get_profile_highlightsinstagram_get_highlight_detailsinstagram_get_post_idinstagram_get_post_detailsinstagram_get_reels_feedinstagram_get_reels_by_audioinstagram_popular_searchinstagram_get_location_postsinstagram_get_nearby_locationsBEFORE YOU INSTALL
What to know first
Tools you get
47 tools named in the project's documentation. Facebook (31) and Instagram (16) only, all reads with no posting. limit is capped at 9 per call on page posts, so 30-day engagement rates and cross-brand comparisons take several calls.
Requires
- npx on PATH
- SOCIALAPIS_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g @socialapis/mcpMCP Clients
Claude Desktop — key as argument
CLAUDE DESKTOP — KEY AS ARGUMENT · JSON
{
"mcpServers": {
"socialapis": {
"command": "npx",
"args": [
"-y",
"@socialapis/mcp",
"<YOUR_API_KEY>"
]
}
}
}
