rozetka-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROZETKA_COUNTRY | No | Rozetka country setting. | UA |
| ROZETKA_LANGUAGE | No | Rozetka language setting. | ua |
| ROZETKA_FRONT_TYPE | No | Rozetka front type setting. | xl |
| ROZETKA_HTTP_RETRIES | No | Number of HTTP retries. | 2 |
| ROZETKA_HTTP_TIMEOUT_MS | No | HTTP timeout in milliseconds. | 15000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rozetka_search_productsB | Search Rozetka.ua through its public-facing JSON search backend. No browser automation. Rich hydration is best-effort and never required. |
| rozetka_get_productA | Resolve one Rozetka product by numeric id or product URL. Description and characteristics are fetched by default from product-api; blocked optional catalog hydration does not fail the lookup. |
| rozetka_get_productsB | Resolve up to 60 Rozetka product ids. Rich catalog hydration is attempted when available and falls back to public search/id records when blocked. |
| rozetka_list_filtersA | Return Rozetka's live filter metadata/options for a search query. Use this before passing category-specific keys in rozetka_search_products.filters. |
| rozetka_list_categoriesB | Return category suggestions from Rozetka's search API for a text query. Full fat-menu enumeration is intentionally not used because common-api may be Cloudflare-protected. |
| rozetka_resolve_urlA | Resolve a Rozetka product URL (/p/) or category URL (/c/) without a network request. |
| rozetka_saved_search_listB | List locally saved Rozetka searches. |
| rozetka_saved_search_createC | Save a structured Rozetka search locally for repeat execution. |
| rozetka_saved_search_runC | Run a locally saved Rozetka search. |
| rozetka_saved_search_deleteC | Delete a locally saved Rozetka search. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools target distinct resources or actions, but get_product vs get_products and get_product vs resolve_url for URL inputs create mild overlap. Descriptions generally clarify boundaries, so misselection risk is low but not zero.
All names use snake_case with a rozetka_ prefix, which is good. However, product tools follow verb_noun (get_product, search_products, list_filters) while saved-search tools follow noun_verb (saved_search_list, saved_search_create, saved_search_delete, saved_search_run), creating a clear mixed convention.
10 tools are well-scoped for a product search/catalog and saved-search wrapper. The set covers core retrieval, search support, URL resolution, and saved-search lifecycle without excessive or trivial tools.
The surface covers search, single/batch product fetch, filters, categories, URL resolution, and saved-search create/list/run/delete. Minor gaps remain: no update/rename for saved searches and no dedicated category-browse operation beyond search.