Skip to main content
Glama
fjvalencian

Facebook Marketplace MCP

by fjvalencian

search_listings

Search for items on Facebook Marketplace using keywords, location, and filters like price, condition, and category.

Instructions

Search Facebook Marketplace listings by query, location, and filters

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax number of results (default: 20)
queryYesSearch query (e.g. 'bmw e30', 'macbook pro')
cursorNoPagination cursor from a previous search's 'next cursor' to fetch the following page
sort_byNoOrder the returned results: best_match (default), price_asc, price_desc, date_desc (newest first)
categoryNoCategory ID to filter by
latitudeYesLatitude of search center
conditionNoFilter by item condition (server-side)
longitudeYesLongitude of search center
max_priceNoMaximum price filter, in the listing's currency units (e.g. CLP pesos, USD dollars)
min_priceNoMinimum price filter, in the listing's currency units (e.g. CLP pesos, USD dollars)
radius_kmNoSearch radius in kilometers (default: 50)
price_scaleNoAdvanced: multiplier applied to min_price/max_price before sending to Facebook. Facebook uses a 2-decimal minor unit for ALL currencies (including CLP/JPY), so the default 100 is almost always correct. Only override if price filtering behaves oddly in a specific market. Default: 100
days_since_listedNoOnly show items listed within the last N days
Behavior2/5

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

With no annotations, the description must disclose all behavioral traits, but it only mentions search parameters. It omits important behaviors like pagination (though cursor is in schema), rate limits, authentication, or what the response contains. The description adds minimal behavioral context beyond the schema.

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

Conciseness3/5

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

The description is a single sentence, which is concise but lacks structure. It does not front-load critical information like result format or use cases, and the brevity sacrifices completeness for terseness.

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

Completeness2/5

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

Given the complexity (13 parameters, no output schema, no annotations), the description is inadequate. It fails to explain return values, error handling, or how filters interact, leaving significant gaps for an agent to use the tool correctly.

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% with all 13 parameters documented, so the description need not add much parameter detail. It does not provide any additional semantic meaning beyond what the schema already offers, resulting in a baseline score of 3.

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?

The description clearly states the action ('Search Facebook Marketplace listings') and the inputs ('by query, location, and filters'), making the tool's purpose immediately identifiable and distinguishing it from siblings like 'get_listing' or 'monitor_search'.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as 'get_listing' for single listings or 'monitor_search' for monitoring. The description lacks any context about prerequisites, when not to use, or which sibling tools to consider instead.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fjvalencian/marketplace-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server