Tracking: Get Events
get_package_details[Tracking / Logistics]
[What it does] Reads the logistics status, attention flag, and carrier event snapshot that DSers holds for one tracking number on the authenticated account.
[When to use] Use it when the user asks where a shipment is or why it has stalled, and whenever the agent needs event evidence before handling a delivery exception or replying to a buyer. Trigger words: where is my package, check this tracking number, delivery exception, when will it arrive.
[When not to use] It looks up tracking numbers only and cannot return every package on an order; get the tracking number from get_order first. To write a tracking number back to a store order, use sync_existing_tracking_numbers_to_store. External numbers outside this account cannot be queried.
[How to use]
tracking_numberis required and must belong to this account; a number supplied by a buyer cannot be looked up directly.Events are not necessarily newest first; compare timestamps to identify the latest checkpoint.
Event times use the carrier's own format; a normalized timestamp and timezone appear only when available, so confirm the timezone before comparing times.
An empty event list is a valid result meaning no scans yet; it does not prove the parcel is unshipped or lost. Estimated delivery is not returned and must not be inferred.
The data is a stored DSers snapshot that can lag the carrier site. The attention flag is only a marker, not a confirmed exception. [Side effects] None; read-only. [Confirmation] Not required.
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": {
"tracking_number": "<tracking_number>"
},
"name": "get_package_details"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tracking_number | Yes | Copy tracking number from list_packages results. Required. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| events | Yes | Tracking events; use event timestamps to determine chronological order | |
| attention | Yes | Whether marked for attention | |
| tracking_status | Yes | Current logistics status | |
| toolcall_response_at | Yes | UTC timestamp when the Tool response was returned, formatted as RFC3339. |