Facebook MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FACEBOOK_PAGE_ID | Yes | Your Facebook Page ID | |
| FACEBOOK_PAGE_ACCESS_TOKEN | Yes | Your Facebook 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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| post_to_facebookC | Posts a message to the Facebook Page |
| reply_to_commentC | Replies to a comment on a specific post |
| get_page_postsC | Retrieves posts published on the Facebook Page |
| get_post_commentsB | Retrieves comments for a specific post |
| filter_negative_commentsB | Filters negative comments from a post |
| delete_postC | Deletes a post from the Facebook Page. |
| delete_commentB | Deletes a comment from a post. |
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 7 tools
All 7 tools serve distinct and clearly defined purposes, with no overlap. Each tool targets a specific action on a specific resource (posts or comments), making selection unambiguous.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., delete_comment, get_page_posts), providing a predictable and logical naming scheme.
With 7 tools, the set is well-scoped for managing Facebook Page content. It covers essential operations without unnecessary duplication or bloat.
The tool set covers create, read, and delete for posts and comments, plus filtering and replying. The only notable gap is the absence of update operations (e.g., update_post, update_comment), but the core workflow is supported.