olx-mcp-api
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OLX_BASE_URL | No | Base URL for the target OLX country. Values include https://www.olx.pl (Poland, default), https://www.olx.ro (Romania), https://www.olx.pt (Portugal), https://www.olx.bg (Bulgaria), and https://www.olx.ua (Ukraine). | https://www.olx.pl |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_offersA | Search OLX offers via the public JSON API. Location/category must be numeric IDs — get them with resolve_olx_url (e.g. "/elektronika/krakow/") if you only know names. Returns compact offers plus total count and nextOffset. |
| get_offerA | Full details of one offer by its numeric id (the "id" from search_offers): description, all photos, params, seller. |
| resolve_olx_urlA | Convert an olx.pl search URL or path (e.g. "https://www.olx.pl/elektronika/krakow/q-lutownica/?search[dist]=30") into API params (category_id, city_id, region_id, filters). Use the result in search_offers. Experimental endpoint. |
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 3 tools
Each tool has a clearly distinct role: search_offers finds listings, get_offer retrieves full details for one listing, and resolve_olx_url converts human-readable URLs into API parameters. There is no overlap in purpose, and the descriptions explicitly explain how the tools relate.
All tool names use consistent snake_case with a verb_noun structure: get_offer, resolve_olx_url, and search_offers. The inclusion of 'olx' in resolve_olx_url is a minor domain-specific detail but does not break the pattern.
Three tools is a well-scoped set for a read-only search API: one for discovery, one for detail retrieval, and one for input normalization. Each tool earns its place without redundancy.
The surface covers the core read-only workflow of resolving a URL, searching offers, and fetching offer details. Minor gaps exist, such as no direct category/city lookup tools, but resolve_olx_url provides a workaround for common cases.