ru-marketplace-mcp

Browse the Detsky Mir catalog tree and get the aliases `detmir_category` needs. This is the discovery step: Detsky Mir has **no working text search** (see the module docstring), so the way to find products is to walk the tree and then list a category. Each node carries its `alias` and a `products_count`, so you can see where the inventory actually is before fetching a listing. ## Return Format DetmirCategoriesResponse: {parent, returned, total_available, items, region, meta}. Items carry category_id, alias, title, full_name, level, products_count, parent_id, url; alias is what detmir_catego…

List products in a Detsky Mir category, with the total match count. This is the reliable way to enumerate the catalog: unlike text search, it is a real JSON endpoint with proper pagination and an upstream total, so it supports "what's available and how much does it cost" without scraping. ## Return Format DetmirListResponse: {query, mode, total_available, category_title, returned, offset, items, region, meta}. Items carry the same product shape as detmir_card. An empty page is NOT an error — it is reported via meta.warnings. ## Error Format On validation or transport/parse failure, raises…

Fetch one DNS-Shop product card. ## Return Format DnsCardResponse: {status, product_id, title, price_rub, old_price_rub, is_available, url, tier_used, meta}. ## Error Format ToolError: BadRequestError when the URL carries no product id; ChallengeRequiredError on a Qrator wall (never cached); TransportDownError on CDP/navigation failures; ParserDriftError when a rendered card has neither product title nor price and no challenge evidence.

Search DNS-Shop, rendered in the operator's Chrome. ## Return Format DnsSearchResponse: {status, query, tier_used, count, items[], meta}. price_rub is None when absent — never 0. ## Error Format ToolError: ChallengeRequiredError on a Qrator wall (never cached); TransportDownError on CDP/navigation failures; ParserDriftError when a rendered page yields zero product tiles without challenge evidence.

Fetch a GraphQL card over HTTPS, falling back to an in-page Chrome POST. ## Return Format LamodaCardResponse: {status, sku, title, brand, price_rub, old_price_rub, is_available, sizes[], url, tier_used, meta}. Lamoda exposes no ratings. ## Error Format ToolError: BadRequestError when no SKU can be extracted; NotFoundError when the SKU has no product; ChallengeRequiredError when the Chrome fallback lands on Lamoda's anti-bot page (complete it, then retry); TransportDownError on HTTP failures; ParserDriftError when the GraphQL envelope changed.

Search Lamoda, rendered in the operator's Chrome (discovery is blocked tier 1). ## Return Format LamodaSearchResponse: {status, query, tier_used, count, items[], meta}. Items carry sku, title, brand, price_rub (None when absent — never 0), url. ## Error Format ToolError: challenge_required on a visible challenge (not cached); TransportDownError on CDP/nav failures; ParserDriftError when a rendered page yields zero SKUs without challenge evidence.

List which connectors this unified server actually mounted. ## Why this exists Connectors are imported defensively, so a missing dependency removes a marketplace instead of killing the server. That is the right failure mode, but it is invisible from the client: absent tools look the same as a source that simply found nothing. Call this before concluding a marketplace has no results — if it is in ``skipped``, it was never queried at all. ## Return Format MarketplaceSourcesResponse: {mounted, skipped, mounted_count, skipped_count, capabilities, server_version}. ``skipped`` maps source name t…

Fetch one Megamarket product card. ## Return Format MegamarketCardResponse: {status, item_id, title, price_rub, old_price_rub, is_available, rating, rating_count, url, tier_used, _meta}. ## Error Format ToolError: BadRequestError on unparseable input; NotFoundError on a missing goods id; TransportDownError on ServicePipe refusals; ParserDriftError on envelope drift.

Search the Megamarket catalog via the mobile API, inside the operator's Chrome. Prices and availability depend on the delivery address: by default a public city-level one (MEGAMARKET_ADDRESS); only with MEGAMARKET_USE_PROFILE_ADDRESS=1 does the logged-in profile's default address win — that reads a private account endpoint, and the response says so in _meta.warnings ("address_source:profile" plus a "profile_address_read" notice). _meta.healthy is false only for that profile read and for "address_source:none" (no delivery address resolved); the default suggest path answers healthy with no addr…

Fetch per-SKU 30-day sales analytics from MPStats (Ozon or Wildberries). Returns, per SKU: seller/brand identity, current stock and price, a rolling orders-per-day average, aggregated totals over the window, and four per-day graphs (orders, prices, stock count, rubric positions). Graphs are length ``days`` (default 30), oldest-first; a zero cell means "no data for that day", not "the value was zero". Requires the ``MPSTATS_MP_AUTH`` env var (a paid MPStats account JWT cookie). Without it the tool returns an ``auth_missing`` error. ## Return Format MpStatsItemResponse: {place, days, count, …

Fetch per-SKU warehouse stock split from MPStats (Ozon or Wildberries). Returns, per SKU: FBS (seller warehouse) stock count, total FBO (marketplace warehouse) stock count, the raw per-warehouse FBO entries when MPStats populates them, and the upstream ``last_update`` timestamp. Requires the ``MPSTATS_MP_AUTH`` env var (a paid MPStats account JWT cookie). Without it the tool returns an ``auth_missing`` error. ## Return Format MpStatsWarehousesResponse: {place, days, count, items, meta}. Each item carries sku and stocks {fbs, fbo, fbo_warehouses, last_update}. Missing stock counts are None,…

Fetch Ozon product card data via composer-api.bx. Tier-1 (curl_cffi) tried first. Falls back to Tier-2 (Chrome CDP at port 9222) when Tier-1 hits Cloudflare 403. Tier-2 requires the operator running Chrome via scripts/start_chrome_cdp.ps1 (Windows) or scripts/start_chrome_cdp.sh (Linux/macOS) first. ## Return Format OzonCardResponse: {status, price, card_price, price_original, is_available, rating_score, rating_count, title, seller, characteristics, url, tier_used, meta} on success. Fields are None when the page does not carry them. ## Error Format Raises ToolError on validation (BadReque…

Fetch Ozon product review texts + star distribution via composer-api.bx. Tier-1 (curl_cffi) tried first, Tier-2 (Chrome CDP) fallback — same path as ozon_card. Returns review texts (comment/positive/negative), per-review score, helpfulness votes, author first name, date, plus the overall star distribution and total count. Pages are walked automatically (30/page) until `limit` texts are collected or pages run out, deduplicating by review uuid. Hard cap of 10 pages. ## Reviews are pooled per card family, not per product Ozon shows one shared pool for every variant of a card, and those varian…

Search Ozon catalog. Tier-1 curl_cffi → Tier-2 CDP fallback. Returns sku/title/price/rating per item. Schema parses Nov 2026 `tileGridDesktop-*` widgets with `mainState` atom structure. ## Return Format OzonSearchResponse: {status, query, page, tier_used, count, items, meta} on success. Zero matching items is NOT an error — it returns a healthy response with count=0 and empty items. ## Error Format Raises ToolError on validation (BadRequestError), transport/block (TransportDownError), or parser drift (ParserDriftError).

Fetch one Taobao item card. ## Return Format TaobaoCardResponse: {status, item_id, title, price_cny, shop_name, sales, description_images, url, tier_used, meta}. price_cny is None when the page hides it or prices by variant — never 0. When the description-image count drifts to a non-number, description_images degrades to 0 and meta.warnings names the drift — the card itself still answers. ## Error Format ToolError: BadRequestError when no id can be extracted; NotFoundError when the item page reports itself gone; challenge_required on login/CAPTCHA walls; TransportDownError on CDP failures;…

Search Taobao listings, rendered in the operator's Chrome. ## Return Format TaobaoSearchResponse: {status, query, page, tier_used, count, items[], meta}. Items carry item_id (string), title, price_cny (None when hidden — never 0), shop_name, sales label, url. ## Error Format ToolError: challenge_required when a login/CAPTCHA wall needs browser action; retry after completing it in the scraping profile. TransportDownError when Chrome/CDP is unreachable; ParserDriftError for unexplained empty extraction. Challenge pages are never cached as successful search results.

Fetch product card data from WB v4 API. Returns prices in rubles, brand, supplier, supplier_rating, review_rating, feedbacks count, total_quantity for up to 100 SKUs. ## Return Format WbCardResponse: {dest, count, items, meta}. Items carry nm_id, name, brand, supplier, supplier_id, supplier_rating, review_rating, feedbacks, total_quantity, in_stock, price_rub, price_original_rub. price_rub is None when the SKU has no sellable price — never 0. Unknown SKUs are NOT an error — they simply do not appear in items. ## Error Format ToolError: BadRequestError on malformed nm_ids; RateLimitedError…

Browse the Wildberries catalog tree. Use this to discover what exists before searching: `wb_search` needs a query string, but a shopper's question is often "what categories of humidifiers are there?". Each node carries WB's own `shard` and `query` selectors, which are the addressing needed to pull a category feed. The live menu is ~800 KB, so responses are always a bounded slice — start at 'top', then expand the branch you care about. ## Return Format WbCategoriesResponse: {root, max_depth, total_returned, truncated, items, host_used, meta}. Nodes carry id, name, url, shard, query, depth, …

List the products in a catalog category, using the shard and query from wb_categories. This closes the loop `wb_categories` opens. That tool hands back WB's own `shard` and `query` selectors — the address of a category feed — and this is the tool that fetches it. Browsing "what humidifiers exist" no longer requires inventing a search phrase and hoping WB's relevance ranking agrees with you. Items come back in the same shape `wb_search` and `wb_card` return, so a category walk and a text search are directly comparable. **Not every category has a feed.** WB marks those with the shard `blackho…

Fetch buyer questions and seller answers by imt_id (root_id from wb_root_info). Answers this tool exists for: buyers ask what a listing omits — "does it fit a 60cm opening", "is the cable included", "is this the 10A or the 16A model" — and the seller's reply is often the only public statement of that fact. Reviews describe the experience of owning the product; questions clarify what it actually is. Keyed by imt_id, exactly like ``wb_reviews``: every colour and size variant shares one question pool. Passing an nmId returns an empty pool with no error, so resolve the root id via ``wb_root_info…

Fetch reviews by imt_id (root_id from wb_root_info). All product variants share one review pool, indexed by imt_id NOT nmId. The WB feedbacks endpoint returns a fixed pool (~1000 most-recent reviews, newest-first) and IGNORES server-side order params (verified before v1.0.0, July 2026), so `sort` is applied CLIENT-SIDE over that pool. To surface complaints, "worst" reorders the returned pool by lowest rating first. ## Return Format WbReviewsResponse: {imt_id, sort, pool_size, feedback_count, valuation, valuation_distribution, feedbacks, host_used, meta}. Review items carry rating, text, pr…

Fetch full card metadata from basket CDN. Returns imt_id (root_id) for review pool. All variants of one product share imt_id. Reviews indexed by imt_id, NOT by nmId. ## Return Format WbRootInfoResponse: {imt_id, subj_name, subj_root_name, colors, compositions, options, host_used, meta}. imt_id is the root product id shared by every variant — wb_reviews is indexed by it, not by nmId. ## Error Format On validation or transport/parse failure, raises ToolError with a JSON message describing the error code and whether it is retryable.

Search WB catalog by text query. Uses search.wb.ru v9 product data, with a warned legacy IDs/card fallback. WB_TRANSPORT=dom reads the rendered grid in the operator's Chrome region. ## Return Format WbSearchResponse: {query, page, page_size, total_ids, count, items, meta}, with items in the same shape as wb_card. Zero matches — or a page past the end — returns WbNoResultsResponse {status: "no_results", query, page, total_ids} instead. Optional meta reports DOM warnings only when present. That is NOT an error; unknown totals remain null. ## Error Format ToolError: BadRequestError on a page…

Look up the registered legal entity behind a WB seller. Answers "who actually ships this?" — the question a marketplace listing is worst at. Returns the registered name, tax ids (INN/KPP/OGRN) and legal address, which is how you tell an official brand store from a reseller trading under a lookalike name, and how you spot several storefronts sharing one entity. Chain from `wb_card`: its `supplier_id` field feeds straight into this tool. ## Return Format WbSellerResponse: {supplier_id, name, full_name, trademark, inn, kpp, ogrn, legal_address, taxpayer_code, foreign_codes, host_used, meta}. …

Fetch full detail for a Yandex Market product: prices, rating breakdown, reviews. Two things here are hard to get anywhere else. The **star distribution** (`rating_stars`) shows whether a 4.8 average hides a cluster of one-star complaints. And **reviews arrive with the card** in one request, complete with pros, cons and helpfulness votes. Reviews are capped at the ~13 Yandex renders server-side; the remainder load through an API this connector deliberately does not touch. ## Return Format YandexCardResponse: {product_id, sku_id, title, brand, seller, description, image, price_rub, price_wi…

Search Yandex Market and return products with both prices, ratings and sellers. Yandex Market aggregates many sellers per product, which makes it the best single source for "what does this cost right now" across the Russian market — including goods Wildberries and Ozon do not carry. Each result reports `price_rub` (what anyone pays — the price the SERP snippet's cart button charges, cross-verified against product cards) and `price_with_plus` (requires a Yandex Plus subscription, typically 25-30% lower). Prefer `price_rub` when quoting a price to a person; `price_old_rub` is the struck-throug…