Skip to main content
Glama

run_hepsiburada_products_reviews

Fetch Hepsiburada product reviews across all variants, including ratings, text, author, date, verified purchase, helpful count, feature ratings, keywords, and photos. Sort by helpful or recent.

Instructions

Get customer reviews for a Hepsiburada product (aggregated across its variants): rating, text, author, date, verified purchase, helpful count, per-feature ratings, keywords and photos. Sort by most helpful or most recent. 1 point per returned record.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product": "<product>"
    },
    "name": "run_hepsiburada_products_reviews"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort by. Options: MOSTHELPFUL = Most helpful, MOSTRECENT = Most recent
productYesSKU, product group ID or URL. e.g. HBCV00004X9ZCK
max_itemsNoMax reviews (up to 490)
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses the aggregation behavior across variants, the breadth of returned fields, and a non-obvious cost model ('1 point per returned record'). It stops short of covering pagination limits or rate limiting, but the delivery model disclosure is genuinely useful.

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, front-loaded with the payload contents, with the pricing note last. Slight redundancy in restating the sort enum already in the schema, but no wasted prose.

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?

There is no output schema, so the description correctly enumerates the returned fields and the cross-variant aggregation, which an agent needs in order to interpret results. Pagination mechanics are left to the schema, and no billing caveats are expanded, but the essentials are covered.

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 product, sort, max_items and start_page fully. The description re-states the sort options but adds no syntax, format, or edge-case detail beyond the schema, matching the baseline for a fully-documented schema.

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 (Get) and resource (customer reviews for a Hepsiburada product), plus the aggregation scope across variants, which clearly separates it from siblings like run_hepsiburada_products (product data) and run_hepsiburada_products_search (product discovery).

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

Usage Guidelines2/5

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

The description never says when to choose this over the many sibling review tools (e.g. run_trendyol_products_reviews, run_walmart_product_reviews) or when it is inapplicable. The only selection-ish cue is the sort option, which is a parameter, not usage guidance.

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