Skip to main content
Glama

run_hepsiburada_products_search

Search Hepsiburada products by keyword and apply filters for brand, seller, color, price, rating, fast delivery, discounts, and photo reviews, then sort results.

Instructions

Search Hepsiburada products by keyword with filters (brand, seller, color, price range, minimum rating, fast delivery, discounted, photo reviews, authorized sellers) and sorting. 1 point per returned record.

Input Schema

NameRequiredDescriptionDefault
sortNoSort by. Options: artanfiyat = Price: low to high, azalanfiyat = Price: high to low, coksatan = Best sellers, yorumsayisi = Most reviewed, degerlendirmepuani = Top rated, indirimurunler = Biggest discount, enyeni = Newest
brandNoBrand (slug). e.g. apple, samsung
colorNoColor. Options: Siyah = Siyah, Beyaz = Beyaz, Mavi = Mavi, Lacivert = Lacivert, Mor = Mor, Kırmızı = Kırmızı, Yeşil = Yeşil, Sarı = Sarı, Pembe = Pembe, Gri = Gri, Gümüş = Gümüş, Kahverengi = Kahverengi, Turuncu = Turuncu, Bej = Bej, Krem = Krem, Altın = Altın, CokRenk = CokRenk
keywordYesSearch term. e.g. iphone 15
merchantNoSeller name (exact, case sensitive). e.g. Hepsiburada
max_itemsNoMax items (up to 500)
price_maxNoMax price (TRY)
price_minNoMin price (TRY)
rating_minNoMinimum rating. Options: 4.5-max = 4.5 and up, 4-max = 4 and up, 3-max = 3 and up
start_pageNoStarting page
product_typeNoMain category code. e.g. 98 (laptops)
fast_deliveryNoFast delivery
discounted_onlyNoDiscounted only
authorized_sellerNoAuthorized sellers
recently_reviewedNoRecently reviewed (last 10 days)
advantageous_priceNoAdvantageous price
with_photo_reviewsNoWith photo reviews

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It adds useful cost information ('1 point per returned record') beyond the schema, but does not disclose return format, pagination behavior, rate limits, or whether results are read-only.

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 sentences, front-loaded with the core search action and filter/sort capabilities. The cost note is concise and no sentence is wasted.

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?

Given the high schema coverage, the description is sufficient for invoking the tool correctly: keyword is required in schema and optional filters are summarized. The lack of an output schema means return values are not described, but this is a minor gap for a search endpoint.

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%, so the schema already documents all 17 parameters thoroughly. The description names major filter categories and sorting, but adds no syntax or meaning beyond what the schema provides.

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

Purpose5/5

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

States a specific verb and resource: search Hepsiburada products by keyword. It distinguishes itself from sibling tools like run_hepsiburada_products (likely detail), run_hepsiburada_categories_products (category browsing), and run_hepsiburada_merchants_products (merchant filtering).

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?

The description implies usage by saying it searches by keyword, but it does not explicitly state when to use this tool versus alternatives such as category-based or merchant-based Hepsiburada product tools. No when-not conditions or exclusions are provided.

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

Deploy Server

Other Tools