NeuralVerge Business Intelligence

Hepsiburada Products Search

run_hepsiburada_products_search

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

TableJSON Schema

Name	Required	Description
`sort`	No	Sort 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
`brand`	No	Brand (slug). e.g. apple, samsung
`color`	No	Color. 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
`keyword`	Yes	Search term. e.g. iphone 15
`merchant`	No	Seller name (exact, case sensitive). e.g. Hepsiburada
`max_items`	No	Max items (up to 500) Default: 25.
`price_max`	No	Max price (TRY)
`price_min`	No	Min price (TRY)
`rating_min`	No	Minimum rating. Options: 4.5-max = 4.5 and up, 4-max = 4 and up, 3-max = 3 and up
`start_page`	No	Starting page
`product_type`	No	Main category code. e.g. 98 (laptops)
`fast_delivery`	No	Fast delivery
`discounted_only`	No	Discounted only
`authorized_seller`	No	Authorized sellers
`recently_reviewed`	No	Recently reviewed (last 10 days)
`advantageous_price`	No	Advantageous price
`with_photo_reviews`	No	With photo reviews

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026

changedInput schema / properties / brand / description

Previous value: -"Brand (slug). e.g. e.g. apple, samsung"New value: +"Brand (slug). e.g. apple, samsung"

changedInput schema / properties / merchant / description

Previous value: -"Seller name (exact, case sensitive). e.g. e.g. Hepsiburada"New value: +"Seller name (exact, case sensitive). e.g. Hepsiburada"

changedInput schema / properties / product_type / description

Previous value: -"Main category code. e.g. e.g. 98 (laptops)"New value: +"Main category code. e.g. 98 (laptops)"

AddedOct 1, 2026

TDQS

B3.4/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 usefully discloses a cost/pricing behavior ('1 point per returned record'), which is real behavioral value, but says nothing about pagination behavior, required auth, or return format.

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

Conciseness4/5

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

Two compact sentences with the core action front-loaded and the cost note appended. Efficient and free of filler, though the parenthetical filter list is a slight enumeration dump.

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

Completeness3/5

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

For a 17-parameter search tool with full schema coverage but no output schema and no annotations, the description covers purpose, filters, sorting, and cost but omits pagination semantics (start_page/max_items interplay) and any return-shape expectations. Adequate but with clear gaps.

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 all 17 parameters are already documented in the schema, including enums and examples. The description only summarizes the filter categories (brand, seller, color, price, rating, delivery flags) without adding syntax or semantic detail beyond the schema, which is the correct baseline.

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 ('Hepsiburada products') scoped by keyword, clearly distinguishable from detail-style siblings like run_hepsiburada_products. It does not explicitly name those siblings, but the 'search by keyword' framing makes the intent unambiguous.

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?

Usage is implied: it describes a keyword search with optional filter narrowing. However there is no explicit when-to-use, when-not, or reference to alternatives such as run_hepsiburada_products or run_hepsiburada_categories_products, so the agent must infer routing.

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

All NeuralVerge Business Intelligence tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?