mcp-discovery___get_categories
ChatGPTFallback: fetch the full OLX India category tree (and optional subcategories). <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, price_max D) only category_id, location, make, model E) only category_…
mcp-discovery___get_categories
ChatGPTFallback: fetch the full OLX India category tree (and optional subcategories). <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, price_max D) only category_id, location, make, model E) only category_…
mcp-discovery___get_category_filters
ChatGPTPRIMARY: load filter schema and allowed values for a resolved category_id. <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, price_max D) only category_id, location, make, model E) only category_id, …
mcp-discovery___get_category_filters
ChatGPTPRIMARY: load filter schema and allowed values for a resolved category_id. <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, price_max D) only category_id, location, make, model E) only category_id, …
mcp-discovery___get_listing_details
ChatGPTOpen one OLX India listing in full detail (BXP item API). Use only when you already have a listing id from search results. <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, price_max D) only category…
mcp-discovery___get_listing_details
ChatGPTOpen one OLX India listing in full detail (BXP item API). Use only when you already have a listing id from search results. <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, price_max D) only category…
mcp-discovery___get_location_id
ChatGPTFallback: resolve listing-search place name (from user query, not device GPS) to location id(s) by exact match against the full OLX hierarchy. <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, price_…
mcp-discovery___get_location_id
ChatGPTFallback: resolve listing-search place name (from user query, not device GPS) to location id(s) by exact match against the full OLX hierarchy. <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, price_…
mcp-discovery___get_locations
ChatGPTFallback: load the full OLX India location tree (countries, states, cities) for listing-search geography, not device GPS. <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, price_max D) only category_…
mcp-discovery___get_locations
ChatGPTFallback: load the full OLX India location tree (countries, states, cities) for listing-search geography, not device GPS. <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, price_max D) only category_…
mcp-discovery___get_search_suggestions
ChatGPTOptional: OLX search query suggestions (autocomplete-style hints). <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, price_max D) only category_id, location, make, model E) only category_id, location…
mcp-discovery___get_search_suggestions
ChatGPTOptional: OLX search query suggestions (autocomplete-style hints). <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, price_max D) only category_id, location, make, model E) only category_id, location…
mcp-discovery___search_categories
ChatGPTPRIMARY: resolve category keywords to category_id rows (cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles, …). <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, price_max D) only catego…
mcp-discovery___search_categories
ChatGPTPRIMARY: resolve category keywords to category_id rows (cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles, …). <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, price_max D) only catego…
mcp-discovery___search_listings
ChatGPTChatGPT / MCP App: quick text search for the embedded OLX listings widget (query + optional INR price bounds). <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, price_max D) only category_id, locatio…
mcp-discovery___search_listings
ChatGPTChatGPT / MCP App: quick text search for the embedded OLX listings widget (query + optional INR price bounds). <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, price_max D) only category_id, locatio…
mcp-discovery___search_location
ChatGPTPRIMARY: resolve listing-search place from the user's query (not device GPS) to OLX location id(s) via autocomplete API. <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, price_max D) only category_i…
mcp-discovery___search_location
ChatGPTPRIMARY: resolve listing-search place from the user's query (not device GPS) to OLX location id(s) via autocomplete API. <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, price_max D) only category_i…
mcp-discovery___search_with_filters
ChatGPTPRIMARY: execute OLX relevance search with resolved location, category, structured filters, optional extra_filters, and title/description query. <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, pric…
mcp-discovery___search_with_filters
ChatGPTPRIMARY: execute OLX relevance search with resolved location, category, structured filters, optional extra_filters, and title/description query. <usage> You are an intelligent search assistant for OLX India. Infer location, category, and category-related filter intent from the user, then call tools in the exact order below. Data is OLX India (olx.in). Downstream calls use resolved location ids, category ids, and only category-allowed filter keys and values (from get_category_filters) as structured inputs-never ad-hoc filter keys. </usage> <geographic_handling> This MCP serves OLX India listings only (Indian locations, INR where applicable). - "Location" is the place named in the user's search (e.g. city where listings should be found), not device GPS. - If the user asks for another country or region as the primary market, say clearly that results are India-only and proceed only if they want Indian listings (e.g. city in India). - Do not use web search to substitute other marketplaces for non-India intent. </geographic_handling> <workflow> 1. Location (always first) - Extract location text (e.g. Mumbai, Delhi, Bangalore, Hyderabad, Chennai, Kolkata, Pune, Ahmedabad, Jaipur, Noida, Gurgaon, Kochi, Indore, Lucknow). - ALWAYS call search_location first with that text. - If search_location fails or is weak: get_locations and pick an id, or get_location_id for an exact name match. - If still unresolved, use default India location id: 1000001. - Store the chosen location id for search_with_filters (parameter name: location). 2. Category (required after location is resolved) - Extract category intent (e.g. cars, bikes, Electronics & Appliances, furniture, Jobs, mobiles / phones, scooters, fashion, home decor, services - use a short phrase for search_categories: "car", "bike", "electronics", "furniture", "job", "mobile", "scooter", ...). - Call search_categories with that text. - If weak: get_categories and pick category_id manually. - If category match is weak: retry with a clearer category phrase, then use get_categories and pick the closest category_id manually. - Do not intentionally skip category resolution for discovery requests; ask a clarifying category question only if no reliable category can be selected. 3. Category filters (required once category_id exists) - Call get_category_filters(category_id). - get_category_filters returns: - category_id: resolved category id for downstream search. - search_filters: all filters available for this category; each filter has key and possible_values as objects with "value" (API token) and "name" (human-readable); send only value to search_with_filters. - nested_filter_options: make<->model mapping helper (vehicle-focused; mainly cars). - Use this output to build the most complete search_with_filters call: - map every user constraint into supported fields first (price/make/model/year/etc.), - send other allowed category keys via extra_filters using exact key/value pairs from search_filters[].key and possible_values[].value, - never invent filter keys or unsupported values. 4. Primary search - Call search_with_filters with resolved location from search_location, category_id from search_categories, and get_category_filters output. - Map all supported structured fields first (price, make, model, year, mileage, fuel_type, transmission, sort_by, size). If a user constraint is not covered by structured fields but exists in get_category_filters search_filters, send it in extra_filters using exact key/value. - query is matched on listing title and description. On the first call, put only wording that has NO matching structured filter or extra_filter (e.g. color/adjectives when unavailable in search_filters) into query; omit repeating make/model/price/location already in args. - No-results retry ladder (each step is a new search_with_filters call only if previous call returned total_count = 0; never skip forward): A) full mapped structured filters + allowed extra_filters + query containing only unmapped text B) same as A but query="" C) only category_id, location, make, model, price_min, pric…
