Facebook MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HASDATA_API_KEY | Yes | HasData API key, created free at https://app.hasdata.com |
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 |
|---|---|
| hasdata_facebook_profile_getFacebookProfileA | Get Facebook Profile Fetches a public Facebook page or profile by handle (username, @username or numeric profile id) and returns page id, name, username, category, bio, exact likes and talking-about counts, followers and following, website, phone, page owner, profile and cover photo URLs, plus the posts on the page with their text, media, reaction breakdown, comment and share counts. Walks the feed three posts per request via pagination.nextPageToken. Use to enrich company or creator records, verify a brand's reach and contact details before outreach, monitor competitor pages, or build datasets of page metadata. |
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 confusion or overlap. The tool's purpose is clearly defined, and it is the only available operation in the server.
The tool name follows a consistent pattern (hasdata_facebook_profile_getFacebookProfile), but since there is only one tool, there is no basis for evaluating consistency across multiple tools. The naming is descriptive and includes a provider prefix.
Having only one tool feels extremely thin for a server named 'Facebook MCP Server'. The domain of Facebook data is broad, and a single tool for profile fetching does not justify a dedicated server; it would be more appropriate as part of a comprehensive social media toolkit.
The server claims to cover Facebook data but only offers a single tool for fetching profiles. It lacks any other operations such as searching, posting, managing pages, or accessing other resource types like groups or events. This is a severely incomplete surface for the stated purpose.