facebook-pages-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FB_PAGE_ID | Yes | Default Facebook Page ID (numeric) | |
| FB_PAGE_ACCESS_TOKEN | Yes | Long-lived Page Access Token |
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_page_infoA | Retrieve Facebook Page metadata: name, category, follower count, contact info, location, hours, and cover photo. |
| get_page_insightsB | Retrieve page-level analytics (page_views_total, page_fans, page_fan_adds, page_fan_removes, page_actions_post_reactions_total). Supports day/week/days_28 periods and date ranges. NOTE: Legacy metrics page_impressions and page_reach are deprecated as of June 2026. |
| get_published_postsB | Retrieve a paginated list of posts published by the page, including message, image, permalink, shares, and type. |
| get_post_insightsA | Retrieve engagement metrics for a specific post: impressions, engaged users, clicks, reactions by type, and activity by action type. |
| get_post_commentsA | Retrieve paginated comments on a specific post, including author, timestamp, like count, and reply count. |
| get_video_insightsB | Retrieve performance metrics for a specific video: views, impressions, average watch time, total watch time, and reactions by type. |
| get_page_feedA | Retrieve the full page feed including visitor posts (unlike published_posts which only returns page-authored posts). |
| create_postA | Create a new post on the Facebook Page. Supports text posts, link posts, and photo posts. Returns the new post ID. |
| refresh_token_infoA | Inspect the current access token to check validity, expiration date, and granted scopes. Useful for diagnosing auth issues. |
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 9 tools
Tool purposes are mostly distinct, but 'get_published_posts' and 'get_page_feed' both retrieve posts with the difference being inclusion of visitor posts. While descriptions clarify, they could cause confusion. Similarly, separate insight tools for page, post, and video are clear. Overall minor overlap.
Most tools use 'get_' prefix, but 'create_post' and 'refresh_token_info' use different verbs. Among 'get_', suffixes vary between 'info', 'insights', 'posts', 'comments', 'feed', without a strict pattern. This mixed convention is noticeable but still understandable.
9 tools is appropriate for a Facebook Pages API covering essential operations: page info, insights, post retrieval (two flavors), post interactions, video analytics, post creation, and token management. Neither too few nor too many.
The tool set covers reading page data, posts, comments, and insights, and creating posts. However, it lacks update and delete operations for posts, comment management beyond reading, and other page management features. These gaps are notable for a complete page management surface.