Skip to main content
Glama
ihavealotofguap

oskelly-mcp

Search products

oskelly_search_products
Read-onlyIdempotent

Search the oskelly.ru luxury catalog by text query or filters (brand, category, size, price, sale) and get matching product cards with price, condition, sizes, and seller details.

Instructions

Search the oskelly.ru luxury marketplace catalog and return matching product cards (id, brand, category, price, discount, condition, in-stock sizes, seller, image, URL). Supports full-text query, faceted filtering (brand, category, size, condition, collection, model, seller type, boutique, price range, boolean tags such as sale/vintage/outlet), pagination and sorting. Use oskelly_search_facets first when you need to know which filter values are available, and oskelly_filter_values to resolve names to ids.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number.
priceNoPrice range in RUB; at least one of lower/upper must be set. NOTE (verified live): the backend matches this per size/SKU, not against the card price. A product matches if ANY of its sizes is priced inside the range, and the returned card `price` is the cheapest size — so a card price may fall outside the requested range. Compare against `sizePriceRange` on each result to see the actual span.
queryNoFull-text query, e.g. "gucci сумка". Omit to browse the catalog without a text query.
sizeIdsNoSize value ids (from oskelly_filter_values code='size').
sortingNoNEW = newest first, PRICE_ASC / PRICE_DESC = by price, SCORE_DESC = by relevance (only meaningful with a query), PERSONALIZED = site's own ranking.NEW
verboseNoReturn the raw upstream payload instead of the compact projection. Much larger.
brandIdsNoBrand ids (from oskelly_list_brands or oskelly_filter_values code='brand').
modelIdsNoModel ids (from oskelly_filter_values code='model').
sellerIdsNoRestrict results to specific seller account ids.
pageLengthNoItems per page (1-60). Keep small to limit response size.
categoryIdsNoLeaf/branch category node ids (from oskelly_category_tree).
baseCategoryNoRoot segment node id from the category tree: 2 = Женское, 105 = Мужское, 188 = Детское, 366 = Лайфстайл. These are real tree node ids — read them from oskelly_category_tree rather than assuming. Omit to search all segments.
conditionIdsNoCondition ids: 1 = Новое с биркой, 2 = Отличное, 3 = Хорошее.
extraFiltersNoEscape hatch: raw filter entries merged into the request body verbatim, for facet codes discovered via oskelly_search_facets that this schema does not name yet.
collectionIdsNoCollection ids: 5 = Новая коллекция, 6 = Sale, 7 = Аутлет.
sellerTypeIdsNoSeller type ids (from oskelly_filter_values code='sellerType').
booleanFiltersNoBoolean facet toggles, e.g. {"sale": true, "vintage": true}. Available codes: sale, oskellyChoice, streetwear, newCollection, inStock, outlet, carry_over, celebrity_wardrobe, investment, vintage, brandNew, resale, exclusiveSelection, currentCollection
boutiqueLocationTagIdsNoOSKELLY boutique location ids (from oskelly_filter_values code='boutiqueLocationTag').
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds the return-card field list and enumerates filtering, pagination, and sorting capabilities, giving a clear behavioral model. No contradiction with annotations.

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

Conciseness5/5

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

The description is three sentences, front-loaded with the action and resource, followed by capabilities and sibling guidance. Every sentence earns its place with no redundant filler.

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?

For an 18-parameter search tool with no output schema, the description gives a compact but sufficient overview: output fields, supported filter types, pagination/sorting, and helper-tool pointers. The rich schema carries per-parameter details, so the description does not need to enumerate them.

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%, with detailed per-parameter descriptions such as the price-range per-size matching behavior and id source endpoints. The description adds only a high-level summary of filter dimensions, which is useful but not necessary given the schema. Baseline 3 applies.

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 opens with 'Search the oskelly.ru luxury marketplace catalog and return matching product cards', naming a specific verb, resource, and output fields. It also distinguishes itself from siblings by directing use of oskelly_search_facets and oskelly_filter_values for filter discovery.

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?

It explicitly says 'Use oskelly_search_facets first when you need to know which filter values are available, and oskelly_filter_values to resolve names to ids', giving concrete when-to-use guidance for related tools. It does not cover every alternative such as oskelly_get_product for single-item lookups, but the main discovery workflow is clearly addressed.

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/ihavealotofguap/oskelly-mcp'

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