fbmarket-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FB_PASS | Yes | The Facebook password for the dedicated burner account. | |
| FB_USER | Yes | The Facebook username/email for the dedicated burner account used to access Marketplace. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_daily_digestA | New listings and price drops from a given day, with their scores. This is the main entry point -- ask for it each morning. Defaults to today and to the min_rating in your config. |
| get_watchlistB | Currently-listed vehicles ranked best-first, with how long each has been up. A high-scoring listing with a long days_on_market is the classic negotiating position: the seller has had no luck and knows it. |
| get_listing_historyB | Full timeline for one listing: every observation, every price change. |
| get_compsA | What comparable vehicles are asking, from your own collected history. Widens by +/-2 model years and +/-40,000 km. Needs roughly three weeks of daily scans before the numbers mean anything; the response says so when the sample is thin. |
| analyze_sale_triggersA | What correlates with a vehicle leaving the market fast, in your own data. Cross-references days-on-market against price-versus-comps, price-drop history, vehicle type, price band, and seller phrasing. Reports its own sample size first -- with less than a few weeks of collection the answers are noise and it will say so. |
| get_collection_statusD | How much data has been collected, and how far to trust the analytics yet. |
| list_searchesA | The saved searches in config.toml and how many listings each has produced. |
| search_listingsA | Search Facebook Marketplace live, right now. Hits Facebook, so it is rate-limited and takes a few seconds. Results are NOT written to the tracking database -- use this for one-off questions and let the daily scan do the collecting. |
| run_daily_scanA | Run the daily crawl now instead of waiting for the scheduled job. Slow (minutes, deliberately). Normally Task Scheduler calls this via
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |