Social Fetch

Search Facebook Marketplace listings

facebook_marketplace_search_list

Read-only

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

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Alias for `query`. Prefer `query`.
`lat`	No	Latitude for the marketplace search location.
`lng`	No	Longitude for the marketplace search location.
`sort`	No	Alias for `sortBy`. Prefer `sortBy`.
`trim`	No	Ignored if this tool does not support it.
`count`	No	Deprecated alias for `limit`. When both are set, `limit` wins.
`limit`	No	Optional number of listings to return (1–100). Prefer this over `count`.
`query`	No	Search query text for marketplace listings.
`cursor`	No	Opaque pagination cursor returned by a previous response.
`offset`	No	Ignored if this tool does not support it.
`sortBy`	No	Optional sort order for marketplace listings. `suggested`: Facebook's default relevance ranking. `distanceAscend`: nearest first. `creationTimeDescend`: newest listings first. `priceAscend`/`priceDescend`: lowest/highest price first.
`context`	Yes	Describe the user's underlying goal in one sentence — not the tool you are calling.
`keywords`	No	Alias for `query`. Prefer `query`.
`maxPrice`	No	Optional maximum listing price. Must be greater than or equal to `minPrice` when both are set.
`minPrice`	No	Optional minimum listing price. Must be less than or equal to `maxPrice` when both are set.
`pageSize`	No	Alias for `count`. Prefer `count`.
`radiusKm`	No	Optional search radius in kilometers.
`condition`	No	Optional item condition filter for marketplace listings.
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`dateListed`	No	Optional 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.
`maxResults`	No	Alias for `count`. Prefer `count`.
`max_results`	No	Alias for `count`. Prefer `count`.
`availability`	No	Optional availability filter for marketplace listings.
`deliveryMethod`	No	Optional delivery method filter for marketplace listings.
`conversation_id`	No	Echo 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.

Changed9 schema fields changedSep 21, 2026

addedInput schema / properties / keywords

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Alias for `query`. Prefer `query`."
+}

addedInput schema / properties / maxResults

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Alias for `count`. Prefer `count`."
+}

addedInput schema / properties / max_results

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Alias for `count`. Prefer `count`."
+}

addedInput schema / properties / offset

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

addedInput schema / properties / pageSize

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Alias for `count`. Prefer `count`."
+}

addedInput schema / properties / q

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Alias for `query`. Prefer `query`."
+}

addedInput schema / properties / sort

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Alias for `sortBy`. Prefer `sortBy`."
+}

addedInput schema / properties / trim

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "number"
+    },
+    {
+      "type": "boolean"
+    }
+  ],
+  "description": "Ignored if this tool does not support it."
+}

changedInput schema / required

Previous value: -[
-  "query",
-  "context",
-  "llm_model"
-]New value: +[
+  "context",
+  "llm_model"
+]

Changed5 schema fields changedSep 5, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Describe the user's underlying goal in one sentence — not the tool you are calling.",
+  "type": "string"
+}

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "Echo 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.",
+  "type": "string"
+}

addedInput schema / properties / llm_model

Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "query"
-]New value: +[
+  "query",
+  "context",
+  "llm_model"
+]

Changed1 schema field changedAug 27, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed2 schema fields changedAug 4, 2026

changedInput schema / properties / count / description

Previous value: -"Optional number of listings to return."New value: +"Deprecated alias for `limit`. When both are set, `limit` wins."

addedInput schema / properties / limit

Added value: +{
+  "description": "Optional number of listings to return (1–100). Prefer this over `count`.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

Changed1 schema field changedJul 31, 2026

changedInput schema / required

Previous value: -[
-  "query",
-  "lat",
-  "lng"
-]New value: +[
+  "query"
+]

Changed5 schema fields changedJul 29, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedInput schema / properties / dateListed / description

Previous value: -"Optional date-listed filter for marketplace listings."New value: +"Optional 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."

changedInput schema / properties / maxPrice / description

Previous value: -"Optional maximum listing price."New value: +"Optional maximum listing price. Must be greater than or equal to `minPrice` when both are set."

changedInput schema / properties / minPrice / description

Previous value: -"Optional minimum listing price."New value: +"Optional minimum listing price. Must be less than or equal to `maxPrice` when both are set."

changedInput schema / properties / sortBy / description

Previous value: -"Optional sort order for marketplace listings."New value: +"Optional sort order for marketplace listings. `suggested`: Facebook's default relevance ranking. `distanceAscend`: nearest first. `creationTimeDescend`: newest listings first. `priceAscend`/`priceDescend`: lowest/highest price first."

Changed21 schema fields changedJul 29, 2026
- removedInput schema / properties / count / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
```
- addedInput schema / properties / count / maximum
```
Added value: +100
```
- addedInput schema / properties / count / minimum
```
Added value: +1
```
- addedInput schema / properties / count / type
```
Added value: +"integer"
```
- removedInput schema / properties / lat / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
```
- addedInput schema / properties / lat / maximum
```
Added value: +90
```
- addedInput schema / properties / lat / minimum
```
Added value: +-90
```
- addedInput schema / properties / lat / type
```
Added value: +"number"
```
- removedInput schema / properties / lng / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
```
- addedInput schema / properties / lng / maximum
```
Added value: +180
```
- addedInput schema / properties / lng / minimum
```
Added value: +-180
```
- addedInput schema / properties / lng / type
```
Added value: +"number"
```
- removedInput schema / properties / maxPrice / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
```
- addedInput schema / properties / maxPrice / minimum
```
Added value: +0
```
- addedInput schema / properties / maxPrice / type
```
Added value: +"number"
```
- removedInput schema / properties / minPrice / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
```
- addedInput schema / properties / minPrice / minimum
```
Added value: +0
```
- addedInput schema / properties / minPrice / type
```
Added value: +"number"
```
- removedInput schema / properties / radiusKm / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
```
- addedInput schema / properties / radiusKm / exclusiveMinimum
```
Added value: +0
```
- addedInput schema / properties / radiusKm / type
```
Added value: +"number"
```
First observedJul 20, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful operational context beyond that: the result is a list and pagination is cursor-based, which matters for invoking the tool correctly on subsequent pages. It does not go into rate limits or auth, but the bar is appropriately lower with annotations present.

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?

Two short sentences with no filler. The core operation and scope are front-loaded, and the pagination note earns its place as the only essential additional behavior to mention.

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?

With 25 parameters, multiple aliases, required context/llm_model, and conversation_id sequencing, the description is minimal for the tool's complexity. It does not orient the agent toward the canonical parameters, required context, or output item shape, and there is no output schema to compensate. The cursor note is useful, but the overall picture is incomplete for such a complex tool.

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 the schema already documents every parameter, including alias preferences (query over q, limit over count) and enum meanings. The description only adds the geospatial framing tying keyword and lat/lng together, which is helpful but stays at the baseline given the schema's thoroughness.

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

Purpose5/5

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

States a concrete operation ('Search Facebook Marketplace listings') and scopes it to keyword plus latitude/longitude, with the return shape described as a list using cursor pagination. This clearly distinguishes it from siblings like facebook_marketplace_item_get (single item) and facebook_marketplace_locations_search (location lookup).

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 implies the use case: search Marketplace listings by keyword near a location. However, it names no alternatives and gives no explicit direction on when not to use this tool, leaving the agent to infer distinctions from sibling names.

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

All Social Fetch tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Search Facebook Marketplace listings

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources