Skip to main content
Glama

OLX offers search

run_olx_offers_search
Read-onlyIdempotent

Search live OLX ads by keyword with category, price, condition, seller type, location, delivery and sort. 1 point per returned record.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "run_olx_offers_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort by. Options: relevance = Relevance, newest = Newest, oldest = Oldest, price_asc = Price: low to high, price_desc = Price: high to low
domainNoMarketplace. Options: olx.pl = olx.pl (Poland), olx.ua = olx.ua (Ukraine), olx.ro = olx.ro (Romania), olx.bg = olx.bg (Bulgaria), olx.pt = olx.pt (Portugal), olx.kz = olx.kz (Kazakhstan), olx.uz = olx.uz (Uzbekistan) Default: olx.pl.
city_idNoCity ID
keywordNoSearch term. e.g. iphone
user_idNoSeller user ID
distanceNoDistance (km around the city)
conditionNoCondition. Options: new = New, almost-new = Almost new, used = Used, refurbished = Refurbished, outlet = Outlet, damaged = Damaged, others = Others
max_itemsNoMax items (up to 500) Default: 25.
max_priceNoMax price (marketplace currency)
min_priceNoMin price (marketplace currency)
region_idNoRegion ID
owner_typeNoSeller type. Options: private = Private sellers, business = Business sellers
start_pageNoStarting page (50 offers per page, up to 20)
category_idNoCategory ID
district_idNoDistrict ID
has_deliveryNoOLX delivery only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/openWorld/idempotent/non-destructive, lowering the bar. The description still adds real value beyond them with 'live OLX ads' (freshness) and a billing disclosure ('1 point per returned record'), which is important behavioral context an agent cannot get from annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with purpose and followed by the cost note. No filler and every phrase (facets, point cost) earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter, all-optional search with 100% schema coverage, no output schema, and safety annotations already present, the description covers purpose, filterable facets, and billing. It stops short of noting defaults (olx.pl domain, 25 items, 50/page pagination) or that keyword is optional, but those live in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with enums documented inline (sort, domain, condition, owner_type), so the schema carries parameter semantics. The description only lists facet names (category, price, condition, seller type, location, delivery, sort) without adding syntax, defaults, or format detail beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search) and resource (live OLX ads) plus the dimensions it can filter on, so the agent knows exactly what the tool returns. It does not, however, distinguish itself from the sibling run_olx_offers (which fetches specific offers), leaving that boundary implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Search live OLX ads by keyword' implies the use case (keyword-driven discovery), but there is no statement of when to prefer this over run_olx_offers, run_olx_categories, or run_olx_users_offers, and no exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources