Skip to main content
Glama
Sign In
trendyol-mcp

trendyol-mcp

by bevren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

İade Durum Geçmişi (getClaimAudits)

trendyol_get_claim_audits

Retrieves the audit history of a return item, showing status changes, dates, and the executor of each update.

Instructions

Bir iade kaleminin durum geçmişini getirir: önceki/yeni durum, güncelleme tarihi ve işlemi yapan. executorApp="SellerIntegrationApi" entegrasyon üzerinden, "Seller Center Orders BFF" satıcı paneli üzerinden yapılan işlemi gösterir; bunlar dışındaki kayıtlar sizin tarafınızdan yapılmayan işlemlerdir.

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": {
      "claimItemId": "<claimItemId>"
    },
    "name": "trendyol_get_claim_audits"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimItemIdYesİade kalemi ID (getClaims: items[].claimItems[].id)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Since no annotations are provided, the description carries full behavioral burden. It discloses the returned fields and the meaning of executorApp, indicating a read operation. However, it omits potential edge cases like empty results or error scenarios.

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?

The description is two sentences, front-loaded with the main purpose, and includes necessary details without extraneous text.

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?

Given no output schema, the description adequately lists returned fields (status history, date, operator) and explains the executorApp distinction. It could mention response structure or pagination, but it's sufficiently complete for a simple audit query.

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

Parameters5/5

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

The parameter claimItemId has 100% schema coverage. The description adds valuable context: 'İade kalemi ID (getClaims: items[].claimItems[].id)', explaining where to find the value, which goes beyond the schema's minimal label.

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?

The description clearly states the tool retrieves the status history of a claim item, including previous/new status, update date, and operator. It explains the executorApp field and distinguishes this from siblings like trendyol_get_claims.

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 explicit guidance on when to use this tool versus alternatives (e.g., when to call after getting claims or before approving). The description only explains how to interpret results, not usage context.

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