avito-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AVITO_CITY | No | Avito city slug. `Екатеринбург` and `Екб` also work. Per-call `city` overrides it. | ekaterinburg |
| AVITO_PROXY | No | Optional Playwright proxy server URL. No proxy rotation. | |
| AVITO_TIMEOUT | No | Navigation timeout in seconds (10–90), plus up to 15 seconds for rendering. | 45 |
| AVITO_COOLDOWN | No | Pause after an unresolved access challenge (minimum 60), persisted across restarts. | 600 |
| AVITO_HEADLESS | No | `0` shows the server's browser; requires a desktop display. | 1 |
| AVITO_CACHE_DIR | No | Browser state and pause marker. Created directory mode 0700; session files 0600. | $XDG_CACHE_HOME/avito-mcp or ~/.cache/avito-mcp |
| AVITO_IDLE_TIMEOUT | No | Close Chromium after this many idle seconds (minimum 30). | 300 |
| AVITO_MIN_INTERVAL | No | Seconds between page reads in this process; minimum 3. Parallel tools share one browser lock. | 4 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_listingsA | Search Avito's computer-goods category, default Екатеринбург. Includes new/used/unknown. Price window, sorting and seller filter are checked against the site's controls. Returns one site page (up to 50 listings), asking prices, links, seller ratings, snippet text and lexical hardware signals. local_only filters by listing URL city. total_found is BEFORE local filters. Use get_listing to confirm condition and health claims. |
| get_listingA | Read a full Avito listing URL: price, seller-declared condition, model/parameters, description, seller rating/type and quoted defect/mining/repair/testing mentions. No phone reveal, login, messaging or purchase. A visible listing may already be sold. |
| search_used_partsA | Find used PC parts by checking the actual condition in full listing cards. One search plus up to 5 card reads (default 3). Only structured condition Б/у passes; new/unknown items are excluded and counted. Broken/repair items remain and carry text signals. This is a bounded scan of ONE page, not exhaustive or globally cheapest. Continue with next_offset on the SAME page, then next_page. Results can shift between calls. |
| compare_listingsA | Refresh up to five exact listings side by side. No automatic bargain/risk score. Compare model, memory, condition, included accessories and quoted defects before prices. |
| get_statusA | Local status: default city, saved browser session, request count and access cooldown. Does not contact Avito or disclose cookies, tokens or account data. |
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 5 tools
Most tools have clearly distinct roles: get_listing reads one listing, compare_listings compares up to five, get_status reports local state. search_listings and search_used_parts overlap because both search Avito, but the specialized condition-filtered purpose of search_used_parts is explained well enough to reduce confusion.
Names consistently use snake_case with a leading verb (get_, search_, compare_), which is predictable. Minor deviations include singular/plural noun forms (get_listing vs search_listings) and the extra adjective in search_used_parts, but the pattern remains readable.
Five tools are well-scoped for a read-only Avito listing research server: general search, used-parts search, single-listing read, comparison, and local status. Each tool has a clear place and the set is neither thin nor bloated.
The surface covers the core read-only workflow: search listings, find used parts by condition, inspect a listing, compare exact listings, and check local status. Minor gaps remain, such as no dedicated seller/profile retrieval or category discovery, but agents can work around these via existing search and listing reads.