listam-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LISTAM_LANG | No | Site language: en, hy or ru. Some fields (dates, description) are parsed best in en. | en |
| LISTAM_RATES | No | Approximate AMD per currency unit, used for cross-currency price filters. | USD=363.5,EUR=425,RUB=4.3 |
| LISTAM_TIMEOUT | No | HTTP timeout in seconds. | 20 |
| LISTAM_DATA_DIR | No | Where the saved-search database lives. | ~/.listam-mcp |
| LISTAM_CACHE_TTL | No | Seconds to cache fetched pages. | 300 |
| LISTAM_USER_AGENT | No | User-Agent header. | |
| LISTAM_MAX_RETRIES | No | Retries (with growing backoff) after a 403/429 before giving up. | 2 |
| LISTAM_MIN_INTERVAL | No | Minimum seconds between requests to list.am. | 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_listingsA | Search list.am listings in any category. Price filters are applied locally to the fetched pages using approximate exchange rates, so fetch more pages when filtering heavily. |
| search_by_urlA | Fetch results for an existing list.am search URL, keeping all its filters. |
| get_listingA | Get full details of one listing: price, attributes, description, seller, images, dates. |
| get_listingsA | Get full details of several listings in one call (fetched one at a time, throttled). Use this to check a handful of candidates from a search instead of calling get_listing repeatedly. |
| list_categoriesA | List list.am categories (ID and name). Pass a category_id to see its subcategories. |
| get_filtersA | List a category's own filters (condition, rooms, mileage, transmission...) and their values. Each filter's |
| save_searchC | Save a search so check_saved_search can report only new listings later. |
| check_saved_searchA | Return listings that appeared since the last check of a saved search. The first check records a baseline and returns everything currently listed. |
| list_saved_searchesB | List saved searches with their last check time. |
| delete_saved_searchB | Delete a saved search and its seen-listing history. |
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
Tools are largely distinct by resource+action. The main potential confusion is between get_listing and get_listings, and between search_listings and search_by_url, but descriptions explicitly clarify when to use each (bulk vs single, native filters vs existing URL).
All tools use a consistent snake_case verb_noun pattern (get_listing, list_categories, save_search, delete_saved_search, etc.). Singular/plural variants are intentional and clear.
Ten tools is well-scoped for a listing-site client: search, detail retrieval, metadata helpers, and saved-search lifecycle. Each tool maps to a distinct user workflow without excess.
The surface covers search (two modes), listing details (single and bulk), categories, filters, and saved-search CRUD. Minor gap: no direct way to update an existing saved search's parameters (must delete and recreate), but core read workflows are complete.