Skip to main content
Glama

search_marketplace

Search multiple secondhand marketplaces for used items using keyword, location, price, condition, size, and color filters.

Instructions

Search for items on secondary marketplaces. Supports: . Returns listing ID, title, price, location, and photo count. Facebook: location-based search, no auth. eBay: keyword search with condition filter, requires API keys. Depop: keyword search with filters for sort, condition, category, brands, sizes, colors (requires Chrome). Poshmark: keyword search with filters for sort, condition, sizes, colors (requires Chrome). Use get_listing_details with a listing ID for full description, all photos, seller info, and shipping options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order (Depop, Poshmark). Options: relevance, newest, most_popular, price_low_to_high, price_high_to_lowrelevance
brandNoFilter by brand (Poshmark only). e.g. "Nike", "Levi's", "Gucci"
limitNoMaximum number of results to return (default: 20). eBay paginates automatically to fetch more than 200 (eBay caps offset + limit at 10,000).
queryYesSearch query (e.g., "stroller", "iPhone 14", "vintage couch")
sizesNoFilter by sizes (Depop, Poshmark). Example: ["S", "M", "L"] or ["US 9", "US 10"]
colorsNoFilter by colors (Depop, Poshmark). Options: black, white, red, blue, green, yellow, orange, pink, purple, brown, grey, cream, multi, silver, gold
offsetNoStarting result offset for pagination (default: 0). eBay only; other marketplaces ignore it.
categoryNoProduct 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.
locationNoCity or area to search (e.g., "san francisco", "nyc", "los angeles")san francisco
maxPriceNoMaximum price filter (optional)
minPriceNoMinimum price filter (optional)
showSoldNoInclude sold/unavailable items in results (default: false)
conditionNoItem 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.
departmentNoFilter by department (Poshmark only). Options: Women, Men, Kids
marketplaceNoMarketplace to search. Options: , or "all" to search all marketplacesfacebook
includeImagesNoInclude full image URLs in results (default: false). Use get_listing_details for full photos.
Behavior4/5

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

No annotations provided, so the description carries the full burden. It discloses behavioral traits: auth needs (eBay API keys, Chrome for Depop/Poshmark), pagination (eBay offset+limit, auto-paginate), and that sold items can be shown. It does not mention rate limits or error handling, but covers key aspects.

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 structured into paragraphs per marketplace with a summary at the start and sibling tool reference at the end. It is relatively concise for the complexity, though there is an empty bullet after 'Supports:' which is a minor formatting issue.

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

Completeness4/5

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

Given 16 parameters, no output schema, and no annotations, the description fairly covers the tool's purpose, supported marketplaces, return fields, and key behavior. It references get_listing_details for extended info. It could mention output format or error scenarios, but is largely complete.

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%, baseline 3. The description adds value by explaining marketplace-specific parameter behavior (e.g., offset only for eBay, category options per platform, condition filter differences). It provides examples and clarifications beyond schema descriptions.

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 tool searches for items on secondary marketplaces, lists supported platforms (Facebook, eBay, Depop, Poshmark) and mentions return fields. It distinguishes itself from the sibling tool get_listing_details, which provides full details.

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

Usage Guidelines4/5

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

The description explains when to use the tool (searching marketplaces) and references get_listing_details for more info. It mentions auth requirements for eBay and browser dependencies for Depop/Poshmark, but does not explicitly state when not to use or alternative tools for specific marketplaces.

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/jlsookiki/secondhand-mcp'

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