Skip to main content
Glama

Ürünleri Listele

trendyol_get_products

List Trendyol seller products with pagination and filter by barcode, stock code, approval status, sale status, archived status, or date range.

Instructions

Satıcının Trendyol ürünlerini sayfalı olarak listeler. Barkod, stok kodu, onay/satış durumu ve tarih filtreleri uygulanabilir.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
sizeNoSayfa başına ürün (en fazla 200)
onSaleNotrue: yalnızca satışta olan ürünler
barcodeNoBarkoda göre filtrele
endDateNoTarih: YYYY-MM-DD, ISO 8601 (ör. 2026-07-01T00:00:00+03:00) veya epoch milisaniye
approvedNotrue: yalnızca onaylı ürünler
archivedNotrue: yalnızca arşivlenmiş ürünler
startDateNoTarih: YYYY-MM-DD, ISO 8601 (ör. 2026-07-01T00:00:00+03:00) veya epoch milisaniye
stockCodeNoStok koduna göre filtrele
dateQueryTypeNostartDate/endDate filtresinin hangi tarihe uygulanacağı
productMainIdNoAna ürün ID değerine göre filtrele
Behavior3/5

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

No annotations provided; description only mentions pagination and filters. Lacks disclosure on rate limits, authentication, error handling, or return structure. Adequate but minimal.

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 concise sentences, front-loaded with main action and filter summary. No wasted words.

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?

With 11 parameters, no output schema, and no annotations, the description is brief. Does not explain pagination defaults, return format, or data types beyond schema. Slightly incomplete for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 91%, and description adds value by summarizing filter types (barcode, stock code, status, dates). One parameter (page) lacks description but is self-explanatory.

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?

Description clearly states tool lists seller's Trendyol products with pagination and filter options (barcode, stock code, status, dates). Distinguishes from siblings focused on claims, orders, brands, etc.

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

Usage Guidelines4/5

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

Description implies usage for general product listing with filters, but does not explicitly mention when to avoid or suggest alternatives like specific filter tools (trendyol_filter_approved_products).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bevren/trendyol-market-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server