Skip to main content
Glama

facebook_marketplace_search

Search Marketplace by keyword + city — filters, isLocal/shipsOutsideRadius, opaque cursor (2 credits). Costs 2 credits. Empty results and failures are never charged. Pass cache=true for a free 24h cache hit (default always fresh).

Input Schema

NameRequiredDescriptionDefault
qYesProduct or keyword to search Facebook Marketplace for.
cacheNoSet true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh.
limitNoHow many listings to return (1–200). Flat 2 credits when details=false; details=true billed as 2 + 2 per listing.
cursorNoOpaque pagination cursor from a previous nextCursor. A cursor this endpoint did not issue is 400 INVALID_CURSOR.
sortByNosuggested | distance | creation_time | price_ascend | price_descend.
detailsNoWhen true, adds description/condition/coordinates/full photo gallery/seller/distanceMiles — billed as 2 + 2 credits per enriched listing (listings the 90s deadline did not reach ship as search cards with truncatedReason=enrich_deadline and are not billed the extra 2). Default false → flat 2 credits; cover photo is still in image.
categoryNoTop-level category slug, e.g. electronics.
locationNoAlias of searchLocation. Prefer searchLocation. Either one is required.
maxPriceNoMaximum price in local currency units.
minPriceNoMinimum price in local currency units.
conditionNonew, like_new, good, fair (comma-separated ok).
radiusMilesNoRadius in miles: 1,2,5,10,20,40,60,80,100,250,500. Does not exclude nationwide shipped inventory.
availabilityNoavailable | sold | all.
deliveryMethodNolocal_pickup | shipping | all. Shipped listings can appear nationwide outside radiusMiles — use local_pickup for nearby-only; rows expose isLocal / shipsOutsideRadius.
searchLocationYesSearch-origin city or place name, e.g. 'Austin, TX'. Required — there is no default city. Echoed on the envelope and inside filters. Not listings[].location. Names that don't resolve to a real place are a definitive 400 UNKNOWN_LOCATION (Facebook would otherwise silently search an unrelated metro) — /v1/facebook/marketplace-location-search finds valid ones.
daysSinceListedNoFacebook calendar-day recency: 1 = since the start of yesterday (not a rolling 24 hours), 7, or 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque pagination cursor from a previous nextCursor."New value: +"Opaque pagination cursor from a previous nextCursor. A cursor this endpoint did not issue is 400 INVALID_CURSOR."
    • changedInput schema / properties / details / description
      Previous value: -"When true, adds description/condition/coordinates/full photo gallery/seller/distanceMiles — billed as 2 + 2 credits per listing. Default false → flat 2 credits; cover photo is still in image."New value: +"When true, adds description/condition/coordinates/full photo gallery/seller/distanceMiles — billed as 2 + 2 credits per enriched listing (listings the 90s deadline did not reach ship as search cards with truncatedReason=enrich_deadline and are not billed the extra 2). Default false → flat 2 credits; cover photo is still in image."
  2. Changed1 schema field changed
    • changedInput schema / properties / searchLocation / description
      Previous value: -"Search-origin city or place name, e.g. 'Austin, TX'. Required — there is no default city. Echoed on the envelope and inside filters. Not listings[].location."New value: +"Search-origin city or place name, e.g. 'Austin, TX'. Required — there is no default city. Echoed on the envelope and inside filters. Not listings[].location. Names that don't resolve to a real place are a definitive 400 UNKNOWN_LOCATION (Facebook would otherwise silently search an unrelated metro) — /v1/facebook/marketplace-location-search finds valid ones."
  3. Changed4 schema fields changed
    • changedInput schema / properties / daysSinceListed / description
      Previous value: -"1 (24h), 7, or 30."New value: +"Facebook calendar-day recency: 1 = since the start of yesterday (not a rolling 24 hours), 7, or 30."
    • changedInput schema / properties / location / description
      Previous value: -"Search-origin city or place name, e.g. 'Austin, TX' (query echo — not each listing's city)."New value: +"Alias of searchLocation. Prefer searchLocation. Either one is required."
    • addedInput schema / properties / searchLocation
      Added value: +{
      +  "description": "Search-origin city or place name, e.g. 'Austin, TX'. Required — there is no default city. Echoed on the envelope and inside filters. Not listings[].location.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "q",
      -  "location"
      -]New value: +[
      +  "q",
      +  "searchLocation"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh."
  5. Changed10 schema fields changed
    • changedInput schema / properties / cache / description
      Previous value: -"Set true to serve from the 24h response cache. Default false — always fetch fresh data."New value: +"Set true to serve from the 24h response cache (0 credits on hit). Default false — always fetch fresh. Envelope includes cached + cachedAt on hits."
    • changedInput schema / properties / condition / description
      Previous value: -"new, like_new, good, fair."New value: +"new, like_new, good, fair (comma-separated ok)."
    • changedInput schema / properties / cursor / description
      Previous value: -"Pagination cursor from a previous nextCursor."New value: +"Opaque pagination cursor from a previous nextCursor."
    • changedInput schema / properties / deliveryMethod / description
      Previous value: -"local_pickup | shipping | all."New value: +"local_pickup | shipping | all. Shipped listings can appear nationwide outside radiusMiles — use local_pickup for nearby-only; rows expose isLocal / shipsOutsideRadius."
    • changedInput schema / properties / details / description
      Previous value: -"Set true for description/condition/coordinates/full gallery (2 + 2 credits per listing). Cover photo is included even when false."New value: +"When true, adds description/condition/coordinates/full photo gallery/seller/distanceMiles — billed as 2 + 2 credits per listing. Default false → flat 2 credits; cover photo is still in image."
    • changedInput schema / properties / details / type
      Previous value: -"string"New value: +"boolean"
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 20, max 200. Flat 2 credits per call."New value: +"How many listings to return (1–200). Flat 2 credits when details=false; details=true billed as 2 + 2 per listing."
    • changedInput schema / properties / location / description
      Previous value: -"City or place name, e.g. 'Austin, TX'."New value: +"Search-origin city or place name, e.g. 'Austin, TX' (query echo — not each listing's city)."
    • changedInput schema / properties / q / description
      Previous value: -"Product or keyword to search for (min 2 chars)."New value: +"Product or keyword to search Facebook Marketplace for."
    • changedInput schema / properties / radiusMiles / description
      Previous value: -"Radius in miles (1–500 discrete values)."New value: +"Radius in miles: 1,2,5,10,20,40,60,80,100,250,500. Does not exclude nationwide shipped inventory."
  6. Changed12 schema fields changed
    • addedInput schema / properties / availability
      Added value: +{
      +  "description": "available | sold | all.",
      +  "type": "string"
      +}
    • addedInput schema / properties / category
      Added value: +{
      +  "description": "Top-level category slug, e.g. electronics.",
      +  "type": "string"
      +}
    • addedInput schema / properties / condition
      Added value: +{
      +  "description": "new, like_new, good, fair.",
      +  "type": "string"
      +}
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "Pagination cursor from a previous nextCursor.",
      +  "type": "string"
      +}
    • addedInput schema / properties / daysSinceListed
      Added value: +{
      +  "description": "1 (24h), 7, or 30.",
      +  "type": "string"
      +}
    • addedInput schema / properties / deliveryMethod
      Added value: +{
      +  "description": "local_pickup | shipping | all.",
      +  "type": "string"
      +}
    • changedInput schema / properties / details / description
      Previous value: -"Set true to fetch full description, photos and coordinates per listing (slower, costs more)."New value: +"Set true for description/condition/coordinates/full gallery (2 + 2 credits per listing). Cover photo is included even when false."
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 20, max 200. Billed per result."New value: +"Max items to return. Default 20, max 200. Flat 2 credits per call."
    • addedInput schema / properties / maxPrice
      Added value: +{
      +  "description": "Maximum price in local currency units.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / minPrice
      Added value: +{
      +  "description": "Minimum price in local currency units.",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / radiusMiles
      Added value: +{
      +  "description": "Radius in miles (1–500 discrete values).",
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / sortBy
      Added value: +{
      +  "description": "suggested | distance | creation_time | price_ascend | price_descend.",
      +  "type": "string"
      +}
  7. Changed2 schema fields changed
    • changedInput schema / properties / details / description
      Previous value: -"Set true to enrich each listing with description, photos and coordinates (2 + 2 credits per listing)."New value: +"Set true to fetch full description, photos and coordinates per listing (slower, costs more)."
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Flat 2 credits per call."New value: +"Max items to return. Default 20, max 200. Billed per result."
  8. Changed1 schema field changed
    • changedInput schema / properties / details / description
      Previous value: -"Set true to fetch full description, photos and coordinates per listing (slower, costs more)."New value: +"Set true to enrich each listing with description, photos and coordinates (2 + 2 credits per listing)."
  9. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return. Default 20, max 200. Billed per result."New value: +"Max items to return. Flat 2 credits per call."
  10. Changed1 schema field changed
    • changedInput schema / properties / cache / description
      Previous value: -"Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true)."New value: +"Set true to serve from the 24h response cache. Default false — always fetch fresh data."
  11. Changed1 schema field changed
    • addedInput schema / properties / cache
      Added value: +{
      +  "description": "Responses are cached for 24 hours by default. Set false to bypass the cache and always fetch fresh data (default true).",
      +  "type": "boolean"
      +}
  12. Added

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full burden and does it well: it discloses the 2-credit cost, that empty results and failures are never billed, that cache hits are free for 24h, and that the cursor is opaque and endpoint-issued. It omits rate limits, auth requirements, and the response envelope shape, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense and front-loaded, leading with what the tool does before costs. It wastes a sentence on redundancy — "(2 credits). Costs 2 credits." repeats the same fact — which prevents a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter paid tool with no annotations and no output schema, the description covers pricing and the cache lever but says nothing about what comes back (nextCursor, rows, filters echo, isLocal flags beyond a passing mention). The schema handles inputs thoroughly, but the return contract is left undescribed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds a little meaning — keyword+city intent, the local/shipsOutsideRadius distinction, and cache semantics — but the per-parameter pricing tiers, radius increments, and enum values are already fully documented in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource plus scope: "Search Marketplace by keyword + city" with filters, local/shipping flags, and cursor paging. It clearly separates this from a single-item lookup like facebook_marketplace_item, but never names a sibling explicitly, so differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives operational guidance on cache=true versus fresh fetches and says empty results and failures are free, which steers invocation. It does not say when to prefer facebook_marketplace_item (item detail) or facebook_marketplace_location_search (resolve a city), so the choice between marketplace siblings is left to the agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.