trendyol-seller-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_productsA | List products in the seller's Trendyol store (read-only). Args: page: Zero-based page number. size: Items per page (the sibling V2 endpoint caps at 100; no explicit cap is documented for this V1 filter). approved: True for approved products only, False for unapproved only, omit for both. barcode: Filter by an exact product barcode. Returns a paged summary with barcode, title, quantity, salePrice, listPrice and approved per product. |
| get_ordersA | List order packages (shipment packages) for the store (read-only). Args: status: Optional filter. Documented values: Created, Picking, Invoiced, Shipped, Cancelled, Delivered, UnDelivered, Returned, AtCollectionPoint, UnSupplied. start_date: 'YYYY-MM-DD' or epoch milliseconds. end_date: 'YYYY-MM-DD' (inclusive) or epoch milliseconds. page: Zero-based page number (API allows pages 0-49). size: Items per page, max 200. include_pii: Customer name and full shipping address are REDACTED by default; set True only when personal data is genuinely needed. Returns a paged summary: orderNumber, status, orderDate, totalPrice, order lines, and the customer's city only (unless include_pii=True). |
| get_customer_questionsA | List customer questions about the store's products (read-only). Args: status: One of WAITING_FOR_ANSWER, WAITING_FOR_APPROVE, ANSWERED, REPORTED, REJECTED. Default lists questions awaiting an answer. page: Zero-based page number. size: Items per page, max 50. Returns question id, text, status, creationDate, productName and webUrl, plus the existing answer text when one exists. Customer user names are not included. |
| answer_questionA | WRITE: publish an answer to a customer question on Trendyol. Refuses unless the environment variable TRENDYOL_ALLOW_WRITES=true is set. The answer is shown publicly to customers; Trendyol requires 10-2000 characters and questions can only be answered once. Args: question_id: The question id from get_customer_questions. text: The answer text (10-2000 characters). |
| update_price_and_stockA | WRITE: batch-update stock quantity and/or prices for existing products. Refuses unless the environment variable TRENDYOL_ALLOW_WRITES=true is set. Args: items_json: JSON array of item objects, e.g. '[{"barcode": "BC123", "quantity": 10, "salePrice": 99.9, "listPrice": 129.9}]' Each item needs "barcode"; "quantity", "salePrice" and "listPrice" are optional (update only what you send). Max 1000 items per call. Returns the batchRequestId Trendyol assigns; the update is processed asynchronously on their side. |
| get_claimsA | List returns/claims (iade talepleri) for the store (read-only). Args: page: Zero-based page number. size: Items per page. Returns claim id, orderNumber, claimDate, overall status and per-item status/reason summaries. Customer names are not included. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool addresses a distinct resource: products, orders, customer questions, claims, and price/stock updates. Though get_customer_questions and answer_question are related, they clearly separate read and write concerns, so no ambiguity exists.
Tool names follow a consistent verb-noun pattern: get_* for read-only operations, and action verbs like answer_ and update_ for writes. The naming is uniform and predictable, enhancing usability.
With 6 tools, the server is well-scoped for a seller-focused MCP. Each tool serves a clear purpose without redundancy, and the count is within the ideal 3-15 range for a domain-specific integration.
The surface covers key seller operations: product listing, order viewing, customer Q&A, price/stock updates, and claims. Minor gaps exist (e.g., no product creation/deletion or order detail individual view), but the provided tools support common workflows effectively.