facebook-marketplace
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FBMP_HOME | No | Directory for the Playwright profile, SQLite DB, and reports | ~/.fb-marketplace-mcp |
| FBMP_LOCALE | No | Browser locale | he-IL |
| FBMP_HEADLESS | No | Set to 0 to watch the browser | 1 |
| FBMP_HOME_LAT | No | Your latitude, used for distance scoring | |
| FBMP_HOME_LNG | No | Your longitude, used for distance scoring | |
| FBMP_LOCATION | No | City name (English/Hebrew), slug, or numeric id | telaviv |
| FBMP_TIMEZONE | No | Browser timezone | Asia/Jerusalem |
| FBMP_MAX_PAGES | No | Page-load cap per compare | 12 |
| FBMP_MAX_DELAY_MS | No | Maximum delay between page loads in milliseconds. Keep it; human pace is the point | 5000 |
| FBMP_MIN_DELAY_MS | No | Minimum delay between page loads in milliseconds. Keep it; human pace is the point | 2500 |
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 |
|---|---|
| marketplace_statusA | Check whether the Marketplace browser session is logged in, plus the active configuration. Call first if other tools fail. |
| marketplace_loginA | Open a visible browser window on Facebook so the USER can log in by hand (Claude never types credentials). Waits until login completes or the timeout passes. Optional: search works logged out. |
| marketplace_searchA | Raw Marketplace search for one query. Use for quick looks; for price comparison or 'find me the best deal' use marketplace_compare instead. Write queries the way local sellers write titles (Hebrew and/or English). |
| marketplace_listingA | Full detail for one listing: description, condition, exact pickup area, delivery options, all photos. Set include_photos to SEE the real photos (check the item matches the title, spot stock photos, damage, serial numbers). |
| marketplace_compareA | Find the best-priced listings for a product and benchmark the market. Sweeps every query variant × sort order, merges, drops irrelevant/sold/reposted listings, groups like-for-like (e.g. 'pro · 256GB'), computes price stats per variant, ranks deals (price vs variant, price drops, recency, condition, distance), opens the top few for details, flags scams (too cheap, prepayment, parts/broken, buy requests, placeholder ₪1 prices) and suggests an opening offer. Pass several query variants: Hebrew + English + model spellings, e.g. ['iphone 13', 'אייפון 13']. Takes about 5-8 s per page; default 3 sorts per query, capped at 12 pages. |
| marketplace_watchB | Save, list or remove a watch: a saved comparison that marketplace_check_watches re-runs to report NEW listings, PRICE DROPS and hits at or below a target price. |
| marketplace_check_watchesA | Re-run saved watches and report only what changed since each one's last check: new listings, price drops, target-price hits. The first check of a watch sets a baseline. |
| marketplace_price_historyA | Local price history recorded by earlier searches: one listing's price changes (by id/URL) or past listings whose title matches some text. Useful for 'has this dropped?' and 'what did these go for last month?'. |
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 8 tools
Most tools have distinct roles (status, login, listing detail, price history). The overlapping pairs — search vs. compare (both retrieve listings) and watch vs. check_watches (two halves of the watch feature) — are explicitly delineated in their descriptions, steering an agent to the right choice, so ambiguity is minor rather than real.
All tools consistently use the marketplace_ snake_case prefix, which is predictable and readable. The only slight deviation is that some use noun forms (status, listing, watch, price_history) while others use verbs (search, compare, login, check_watches), but the pattern is uniform enough not to confuse.
Eight tools is well-scoped for a Marketplace browser-automation server. Each tool earns its place: session handling, search, detail fetch, comparison, watch management, and price history — no redundancy or filler.
The surface covers the full browse/monitor workflow: login, search, detail, benchmark comparison, watch save/list/remove plus re-check, and price history. Minor gaps exist (no tool for contacting a seller or saving an individual listing outside a watch), but core deal-finding workflows are complete.