Secondhand MCP

search_marketplace

Read-onlyIdempotent

Search live secondhand listings across Facebook Marketplace, eBay, Depop, and Poshmark by keyword, then filter by price, condition, size, color, or location to compare used items and find sellers.

Instructions

Search live listings on secondhand marketplaces by keyword. Marketplaces: . Returns up to limit listings with id, title, price, location, seller and a thumbnail; call get_listing_details with an id for the description, every photo and shipping. Requirements: Facebook Marketplace needs no credentials but is local, so pass location as "City, ST"; eBay needs EBAY_CLIENT_ID and EBAY_CLIENT_SECRET in the server environment; Depop and Poshmark need Chrome or Chromium on the machine. Behavior: read-only, no login, no purchases. Facebook may rate-limit repeated searches from one IP, and results for a query are cached for 90 seconds. Errors: a marketplace that fails returns success:false with the reason instead of throwing; an unknown marketplace name lists the valid ones; an empty result usually means the query was too specific, so widen the keywords or drop a price bound before concluding nothing exists. Not for: buying, messaging sellers, saved searches, or new-retail catalogs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sort`	No	Sort order (Depop, Poshmark). Options: relevance, newest, most_popular, price_low_to_high, price_high_to_low	relevance
`brand`	No	Filter by brand (Poshmark only). e.g. "Nike", "Levi's", "Gucci"
`limit`	No	Maximum number of results to return (default: 20). eBay paginates automatically to fetch more than 200 (eBay caps offset + limit at 10,000).
`query`	Yes	Search query (e.g., "stroller", "iPhone 14", "vintage couch")
`sizes`	No	Filter by sizes (Depop, Poshmark). Example: ["S", "M", "L"] or ["US 9", "US 10"]
`colors`	No	Filter by colors (Depop, Poshmark). Options: black, white, red, blue, green, yellow, orange, pink, purple, brown, grey, cream, multi, silver, gold
`offset`	No	Starting result offset for pagination (default: 0). eBay only; other marketplaces ignore it.
`category`	No	Product category. Depop: tops, bottoms, dresses, coats-jackets, footwear, accessories, bags, jewellery, activewear, swimwear. Poshmark: use underscore-separated names like Jackets_&_Coats, Dresses, Shoes, Accessories, etc.
`location`	No	City and state for Facebook Marketplace searches, as "City, ST" — e.g. "Austin, TX", "Portland, OR". Resolve neighborhoods, ZIP codes, metro areas and "near me" to a city and state before calling; a bare city name is ambiguous and may return the wrong state. Non-US: pass city and country. Facebook only — other marketplaces ignore it.	san francisco
`maxPrice`	No	Maximum price filter (optional)
`minPrice`	No	Minimum price filter (optional)
`showSold`	No	Include sold/unavailable items in results (default: false)
`condition`	No	Item condition filter. eBay: new, like_new, good, fair. Depop: new, like_new, excellent, good, fair, used. Poshmark: new (NWT), like_new (NWOT), good, fair. Use "any" for no filter.
`department`	No	Filter by department (Poshmark only). Options: Women, Men, Kids
`marketplace`	No	Marketplace to search. Options: , or "all" to search all marketplaces	facebook
`radiusMiles`	No	How far around the location to search, in miles (default 25, max 500). Facebook only. Widen it for a metro area or a rural town.
`includeImages`	No	Include full image URLs in results (default: false). Use get_listing_details for full photos.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.7.1Sep 8, 2026

changedInput schema / properties / location / description

Previous value: -"City or area to search (e.g., \"san francisco\", \"nyc\", \"los angeles\")"New value: +"City and state for Facebook Marketplace searches, as \"City, ST\" — e.g. \"Austin, TX\", \"Portland, OR\". Resolve neighborhoods, ZIP codes, metro areas and \"near me\" to a city and state before calling; a bare city name is ambiguous and may return the wrong state. Non-US: pass city and country. Facebook only — other marketplaces ignore it."

addedInput schema / properties / radiusMiles

Added value: +{
+  "default": 25,
+  "description": "How far around the location to search, in miles (default 25, max 500). Facebook only. Widen it for a metro area or a rural town.",
+  "type": "number"
+}

First observedv0.4.0Jul 12, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already mark this as read-only and idempotent, and the description reinforces and extends that with concrete behavioral details: no login, no purchases, Facebook rate-limiting, 90-second caching, marketplace-specific credentials, and a defined error pattern. This goes well beyond what annotations alone convey.

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?

The description is dense but well-ordered: purpose, marketplace requirements, behavior, errors, and exclusions. Every sentence carries operational value. One minor blemish is the incomplete "Marketplaces: ." fragment, which appears to be a formatting/placeholder artifact and adds no information.

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

Completeness5/5

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

For a 17-parameter, multi-marketplace tool with no output schema, the description is remarkably complete. It specifies the return fields, marketplace-specific prerequisites, credential requirements, caching and rate-limit behavior, error handling, and clear exclusions. An agent has enough context to invoke the tool correctly and recover from common failures.

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

Parameters4/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 useful cross-parameter context beyond the schema, such as Facebook requiring "City, ST" location, eBay pagination behavior, price-bound tuning for empty results, and the distinction between thumbnails and full photos via get_listing_details. Some duplication exists, but the added meaning justifies a 4.

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 uses a specific verb and resource: "Search live listings on secondhand marketplaces by keyword." It clearly distinguishes itself from get_listing_details by stating that details, photos, and shipping require a separate call, and it explicitly lists what it is not for.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use and when-not-to-use guidance: it directs the agent to get_listing_details for richer item data, and it lists exclusions such as buying, messaging sellers, saved searches, and new-retail catalogs. It also provides practical guidance like widening keywords or dropping price bounds when results are empty.

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

Deploy Server

search_marketplace

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools