Skip to main content
Glama

run_hepsiburada_products_sellers

Retrieve all sellers offering a Hepsiburada product, including seller details, prices, ratings, shipping flags, and the buybox winner for comparison.

Instructions

List all sellers (merchants) offering a Hepsiburada product: seller id, name, price, list price, rating, city, shipping flags and which seller wins the buybox. Flat 5 points per successful run.

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_sellers"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesSKU, product group ID or URL. e.g. HBCV00004X9ZCK

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations, so the description carries the full burden. It usefully discloses the payload contents and the cost model ('Flat 5 points per successful run'), which is real behavioral context, but says nothing about pagination, rate limits, or auth requirements.

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?

One front-loaded sentence leading with the verb, followed by a compact field list and a cost note. Dense but every clause contributes; only the field enumeration borders on list-dumping.

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?

With no output schema, the description correctly takes on the job of explaining return values, and it does so thoroughly. For a simple single-param listing tool it is nearly complete, missing only pagination/volume expectations.

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% and the single 'product' param is fully documented (SKU, product group ID or URL). The description's mention of 'a Hepsiburada product' reinforces but does not extend the schema, so the baseline 3 applies.

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 (List) and resource (sellers/merchants offering a Hepsiburada product) and enumerates the returned fields, so the agent knows exactly what comes back. The 'offering a Hepsiburada product' scoping distinguishes it from sibling run_hepsiburada_merchants, which lists merchants directly rather than per-product.

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 by the purpose: fetch the sellers for a given product. However, the description never names the alternative (run_hepsiburada_merchants, run_trendyol_products_sellers) or states when-not-to-use, so routing is left to inference.

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