Skip to main content
Glama

Hepsiburada Product

run_hepsiburada_products
Read-onlyIdempotent

Get full Hepsiburada product details by SKU, product group id or URL: name, brand, price, list price, discount, images, video, rating, stock, specs, variants, categories, the winning seller and other sellers. 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"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely new behavioral context by disclosing the cost model ('Flat 5 points per successful run') and by enumerating the returned data shape, which is valuable for a paid third-party API call.

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 sentences, front-loaded with the verb and identifier scope, then the payload list and cost note. The long field enumeration is dense but each item earns its place by telling the agent what data comes back.

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?

For a single-parameter read tool with full annotation coverage and a rich return-field list, this is nearly complete; the cost note closes the main open question. The remaining gap is routing against the many hepsiburada_products_* siblings, which the description never addresses.

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 schema already states 'SKU, product group ID or URL. e.g. HBCV00004X9ZCK'. The description repeats the same accepted identifier types without adding format rules, so the baseline 3 applies.

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?

Specific verb (Get) plus resource (Hepsiburada product details) and an enumerated field list covering name, brand, price, images, rating, stock, specs, variants and sellers. The identifier-based scope (SKU, product group id or URL) implies it is the detail endpoint rather than a search, but no sibling is named to make that contrast explicit.

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?

No statement of when to use this versus run_hepsiburada_products_search, run_hepsiburada_products_reviews or run_hepsiburada_products_sellers, and no prerequisites or exclusions. The only usage signal is that an identifier is accepted, which is schema territory rather than guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.