fb-marketplace-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| pingA | Health check. Echoes the message back so you can confirm the server is reachable. |
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 a single tool, there is no possibility of overlap or confusion between tools. The lone 'ping' tool has an unambiguous health-check purpose.
A single tool named 'ping' is trivially consistent since there is no set to be inconsistent with. It is a bare verb rather than a verb_noun pattern, but no convention violation occurs.
One trivial health-check tool is an extreme mismatch for a server purporting to serve Facebook Marketplace. There is essentially no functional surface beyond a reachability check.
The domain (Marketplace listings, search, messaging, etc.) is entirely uncovered; the only operation is a ping. An agent could not perform or even probe any marketplace task with this tool set.