OLX MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| searchListingsC | Search for listings on OLX domains (olx.pt, olx.pl, olx.bg, olx.ro, olx.ua) with various filters including query, category, location, and price range |
| getListingDetailsA | Get detailed information about a specific OLX listing from any supported domain (olx.pt, olx.pl, olx.bg, olx.ro, olx.ua) including description, seller info, and images |
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 2 tools
searchListings and getListingDetails have clearly distinct purposes: one discovers listings, the other retrieves details for a specific listing. There is no overlap in their functionality.
Both tool names follow a consistent camelCase verb_noun pattern: searchListings and getListingDetails. The naming style is uniform and predictable.
With only 2 tools, the server is minimal but well-scoped for a read-only OLX listing lookup service. Slightly thin but each tool covers an essential step in the workflow.
The server covers the core read-only lifecycle: finding listings and then viewing details. Missing operations like category browsing or seller info could be gaps, but the essential search-to-detail path is complete.