citilink-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CITILINK_CITY | No | Default city: an id or a name (e.g., Екатеринбург, Москва, Березовский, Свердловская). A city argument wins over it. | ekat_cl |
| CITILINK_PROXY | No | Proxy URL, e.g. http://user:pass@host:3128 | |
| CITILINK_CACHE_DIR | No | City directory (refreshed weekly) and session cookies (file mode 0600, directory 0700); honours XDG_CACHE_HOME. | ~/.cache/citilink-mcp |
| CITILINK_MIN_INTERVAL | No | Seconds between requests to Citilink (plus up to 0.5 s jitter). Calls from parallel agents queue up. | 2.5 |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_productsA | Search Citilink like the site does: pages of 48, sorting, price window, category, availability. Per item: regular price (null = not sold in the city), strikethrough price,
club price only when the site shows it, bonuses (not a discount), lot size
when sold in lots, the product's own rating next to the group rating the
site shows, units in the area's stores, earliest pickup date, badges and
promo codes, markdown flag. |
| get_productA | Full live card of one product for a city. Prices with labels (regular, strikethrough, club price only when shown on
the site, bonuses, lot), payment terms, the product's own rating with star
split next to the variant-group rating the header shows, Citilink's review
digest, manufacturer part number ( |
| get_reviewsA | Customer reviews: date, stars, pros, cons, text, which variant was bought, source, votes. Also returns the product's own rating and its group's rating (both
unfiltered), so it is clear what a headline number covers. |
| get_questionsA | Customer questions with their answers («Вопрос-ответ»), grouped into threads. Answers are marked when written by a Citilink expert or a brand representative, and when the author bought the product. Author names are never returned. |
| find_markdownA | Markdown and used units («Уценка», "(Б/У)") in a city: by category, or copies of one product. Per item: price, strikethrough price, why it is marked down, completeness, wear, damage, warranty (often 1 month), the id of the new product, units in the area's stores and the earliest pickup date. Store-level detail: get_product with the M-id. Plain search rarely shows these items. |
| compare_productsA | Up to 20 products side by side for one city, in one request. Per product: regular price and the other labelled prices, the product's own
rating next to the group rating the site shows, units in the area's stores,
earliest pickup date, courier fee and date, badges and promo codes.
Ids Citilink does not know are listed in |
| resolve_cityA | Look up Citilink city ids by name (Citilink's own directory, cached for a week). Use an |
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 7 tools
Each tool has a clearly distinct purpose: search, product details, reviews, questions, markdown, comparison, and city resolution. No two tools overlap in functionality, making misselection unlikely.
All tool names follow a consistent verb_noun snake_case pattern (get_questions, search_products, get_product, get_reviews, find_markdown, compare_products, resolve_city). The naming is uniform and predictable.
With 7 tools, the set is well-scoped for a product information and search server. Each tool covers a distinct aspect of the domain without redundancy or bloat.
The surface covers core workflows: searching, viewing details, reviews, Q&A, markdown items, comparisons, and city resolution. Minor gaps exist (e.g., no explicit category listing or promotions tool), but search returns categories and badges/promos are included in product details, so agents can work around them.