Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Facebook Marketplace listings

facebook_marketplace_search_list
Read-onlyIdempotent

Search Facebook Marketplace listings by keyword and location coordinates, with optional price, condition, radius, and sort filters. Use returned cursors to page through additional results.

Instructions

Search Facebook Marketplace listings by keyword near a latitude and longitude. Requires query, lat and lng. Returns a list (use cursor when paginated).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>",
      "lat": "<lat>",
      "lng": "<lng>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "facebook_marketplace_search_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYesLatitude for the marketplace search location.
lngYesLongitude for the marketplace search location.
countNoDeprecated alias for `limit`. When both are set, `limit` wins.
limitNoOptional number of listings to return (1–100). Prefer this over `count`.
queryYesRequired. Search query text for marketplace listings.
cursorNoOpaque pagination cursor returned by a previous response.
sortByNoOptional sort order for marketplace listings. `suggested`: Facebook's default relevance ranking. `distanceAscend`: nearest first. `creationTimeDescend`: newest listings first. `priceAscend`/`priceDescend`: lowest/highest price first.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
maxPriceNoOptional maximum listing price. Must be greater than or equal to `minPrice` when both are set.
minPriceNoOptional minimum listing price. Must be less than or equal to `maxPrice` when both are set.
radiusKmNoOptional search radius in kilometers.
conditionNoOptional item condition filter for marketplace listings.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
categoryIdNoOptional numeric Marketplace category id. Only listings in that category are returned. Listings report their category as `categoryId`.
dateListedNoOptional date-listed filter for marketplace listings. `1`/`last24Hours` both mean the last 24 hours, `7`/`last7Days` both mean the last 7 days, and `30`/`last30Days` both mean the last 30 days — these are separate values Facebook accepts for the same window; prefer the named variants (`last24Hours`, `last7Days`, `last30Days`) for clarity. `all` applies no date filter.
availabilityNoOptional availability filter for marketplace listings.
deliveryMethodNoOptional delivery method filter for marketplace listings.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior, so the description does not need to repeat safety traits. It adds useful behavior by stating that the result is a list and that pagination uses a cursor, though it does not mention rate limits or auth requirements.

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

Conciseness5/5

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

The definition is three short sentences and front-loads the operation, required inputs, and return/pagination behavior. There is no filler or redundant wording.

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 an 18-parameter tool, the description is thin: it says only query, lat, and lng are required, while the schema also requires context and llm_model, and it omits the conversation_id echo obligation. The schema compensates with full descriptions and the return-list/cursor note covers the missing output schema, but the required-parameter summary is incomplete.

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 description coverage is 100%, so all 18 parameters are documented in the schema, including enums, ranges, and the cursor format. The description only repeats the query/lat/lng requirement and cursor pagination, adding no new meaning beyond 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?

The description names the verb 'Search', the resource 'Facebook Marketplace listings', and the keyword-plus-location constraint, so the core operation is unambiguous. It stops short of explicitly differentiating from nearby siblings such as facebook_marketplace_locations_search or facebook_marketplace_item_get.

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?

Usage is implied by 'by keyword near a latitude and longitude' plus the required parameters and cursor pagination hint, but the description never states when to choose this over locations search or item lookup. There are no explicit exclusions or alternative-routing instructions, so the agent must infer selection from the purpose.

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

Deploy Server

Other Tools