Skip to main content
Glama
Sign In
ScrapeUnblocker MCP Server

ScrapeUnblocker MCP Server

Official
by ScrapeUnblocker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Scrape eBay search listings

ebay_search
Read-only

Search regional eBay marketplaces by keyword and get structured JSON listings with prices, condition, seller, shipping, and filters for price, condition, and marketplace.

Instructions

Searches any regional eBay marketplace for keyword and returns the listings as JSON: title, price + currency, condition (with a normalised conditionCode), seller (username, feedback percentage and score), shippingCost, sold, watchers, bids, image and a clean item url. Filter with condition, listing_type, min_price/max_price, free_shipping, seller or category, sort with sort, and page with page/page_size (60, 120 or 240 per page). Set marketplace to search a specific site - prices, currency and availability differ between ebay.com, ebay.de, ebay.co.uk and the rest. When eBay finds no exact match it still serves a full page of its own loosely-related suggestions. That case is reported honestly: exactMatches is false and a notice explains it, so those listings are never mistaken for real matches. Returns JSON. Billed like an API request; listing plugins bill one unit per result page they fetch, so keep max_results modest.

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": {
      "keyword": "<keyword>"
    },
    "name": "ebay_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number. Default: 1.
sortNoOrdering: best_match, newly_listed, ending_soon, price_asc, price_desc. Default 'best_match'. Default: best_match.
sellerNoRestrict the search to one seller's username.
keywordYesSearch phrase, e.g. 'iphone 13' or a part number like '1K0953519A'.
categoryNoeBay category id to search inside, e.g. '131090' for vehicle parts and accessories.
conditionNoItem condition filter: new, open_box, refurbished, used, for_parts. Omit for every condition.
max_priceNoHighest price to include, in the marketplace's currency.
min_priceNoLowest price to include, in the marketplace's currency.
page_sizeNoListings per page - eBay's own page sizes: 60, 120, 240. Default: 60.
marketplaceNoRegional eBay site to search. Prices, currency and availability differ per marketplace. One of: ebay.com, ebay.co.uk, ebay.de, ebay.fr, ebay.it, ebay.es, ebay.nl, ebay.pl, ebay.at, ebay.ch, ebay.be, ebay.ie, ebay.ca, ebay.com.au, ebay.in, ebay.ph, ebay.com.sg, ebay.com.my, ebay.com.hk. Default: ebay.com.
listing_typeNoListing format: all, buy_it_now, auction. Default 'all'. Default: all.
free_shippingNoOnly listings eBay marks as free delivery. Default: false.
proxy_countryNoProxy country the request is sent from (ISO-2, e.g. 'US', 'DE'). Defaults to a country chosen for the marketplace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.12.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / page / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / page_size / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / page_size / minimum
      Added value: +-9007199254740991
  2. Addedv0.4.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld/non-destructive; the description adds real behavioral context beyond them — the no-exact-match fallback where eBay serves loosely related listings flagged by `exactMatches: false` plus a `notice`, and the billing model (one unit per result page fetched). The only weakness is that the cost warning references `max_results`, which is not a parameter name in 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.

Conciseness4/5

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

Front-loaded with purpose and return fields, then filters, then caveats — a sensible ordering with little waste. It loses a point for redundancy: "Returns JSON" is stated at the start and again as a standalone sentence, and the field enumeration partially repeats the filter list.

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 13-parameter scraper with no output schema, the description covers what is returned, how to filter/sort/page, the marketplace-currency implication, the misleading-results fallback, and the cost profile. An agent has everything needed to call it correctly and interpret edge-case responses.

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 baseline is 3. The description adds modest value by grouping the filters and noting that price filters are in the marketplace's currency and that marketplaces differ in price/availability, but it introduces no parameter meaning the schema does not already carry.

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?

Opens with a specific verb + resource + scope ("Searches any regional eBay marketplace for `keyword` and returns the listings as JSON") and then enumerates the exact return fields, which separates it cleanly from siblings like amazon_search, google_shopping and google_search without requiring the agent to open a schema.

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?

Gives concrete operational guidance: which parameters filter, which sort, how to page (with the allowed 60/120/240 sizes), and that `marketplace` should be set when site-specific prices/currency matter. It never states when not to use it or names an alternative tool (e.g. google_shopping or amazon_search), so it stops short of full alternative routing.

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