Commerce-Shopping

PttAVM

by PttAVM

Overview

PttAVM Ürün Arama, PttAVM e-ticaret kataloğunda doğal dille ürün aramanızı sağlar. "kablosuz kulaklık çok satanlara göre sırala" ya da "2 TB SSD, indirimli" gibi isteklerde; marka, kategori, fiyat aralığı, indirim ve varyant (renk/beden) gibi filtreleri sunucu tarafında uygular ve sonuçları görsel ürün kartları olarak (fiyat, marka, puan, ürün görseli ve ürüne gidiş bağlantısıyla) gösterir. Connector salt-okunurdur: yalnızca arama yapar, hiçbir yazma/satın alma/hesap işlemi gerçekleştirmez. Satın alma, ürünün pttavm.com üzerindeki sayfasında tamamlanır.

Tools

find_products

Claude

Fetch product data as TEXT for YOUR analysis — does NOT render anything to the user. Use this for every intermediate/exploratory step: counting matches, comparing options, checking which categories/brands appear, or deciding which filters to apply. It takes the same parameters as `search_products (including user_query — the user's verbatim request, for analytics only). When you have decided the final query+filters, call search_products` ONCE to show the user. Returns JSON {total, count, query, items:[{productId, name, brand, category, price, rating, reviewCount, url}]}. On failure: {type:"error", message}.

get_search_filters

Claude

List available filters (facets) for a query so a search can be refined. `user_query: the user's verbatim request, for analytics only (see search_products

). Returns Markdown listing categories (hierarchical), brands, merchants, price ranges, boolean toggles and product/variant specs, with how to pass each back into

search_products`. On failure: "Error: <msg>".

search_products

Claude

Display PTT AVM products to the USER as an interactive card grid (visible UI). This is the FINAL, USER-FACING display. Call it AT MOST ONCE per reply, and only with the results you actually want the user to see (the final query + filters). Every call paints a NEW grid on screen — calling it twice (e.g. a broad search then a filtered one) leaves BOTH on screen and confuses the user. Do your exploring/analysis FIRST, without rendering: - `find_products — fetch product data as text (no UI) to inspect/compare/decide filters. - get_search_filters — list valid brands/categories/specs for a query. Then decide all filters/sort and call search_products

 ONCE. Filtering is server-side: pass brands, merchants, category, min_price/max_price, has_discount, sort, page, attribute, spec. Never filter/sort the returned items yourself (they are one page of

total). Sort: relevance | price_asc | price_desc | newest | best_seller. size up to 72. user_query

: pass the USER's original request **verbatim** (their exact words, e.g. "ssd aramak istiyorum 2 tb olsun"), separate from the cleaned

query` search term. Used for analytics only — it does not affect the search. Returns JSON ({type:"products", total, query, page, items:[...]}) rendered as cards (with a built-in "Devam et" pagination button). On failure: {type:"error", message}.

Links

Documentation ↗Privacy Policy ↗

App Stats

Tools

Claude

Platforms