Skip to main content
Glama

Tracking: Update Numbers to Store

update_tracking_numbers_to_store
Destructive

[Tracking Number / Fulfillment] [What it does] Adds or updates tracking numbers for selected sales-side order items. Each item supports one or more tracking numbers, which are sent directly to the sales channel. If an item already has tracking numbers, the complete list submitted in this request replaces the existing list. Appending is not supported. [When to use] Use when you need to set new tracking numbers for selected sales-side items in one DSers order or replace their existing tracking numbers. [When not to use] To synchronize tracking numbers already stored on the DSers order, use sync_existing_tracking_numbers_to_store. This Tool cannot append new tracking numbers to the existing list. Use get_package_details to inspect tracking events. Before calling this Tool, use get_order to review the order, sales-side items, and existing tracking numbers. [How to use]

  • Copy dsers_order_id from get_order.

  • Copy each dsers_order_item_id from the order's items[].dsers_order_item_id. Do not use supplier_order_item_id.

  • tracking_updates must be a non-empty array. Each update may target only one sales-side item.

  • Each update's tracking_numbers must be a non-empty array containing one or more tracking numbers.

  • The complete tracking_numbers list in each update replaces the existing tracking numbers of the corresponding item.

  • The same dsers_order_item_id must not appear more than once in tracking_updates.

  • Tracking numbers are trimmed and deduplicated. Empty tracking numbers are rejected.

  • Order ownership and item membership are validated before the update is sent.

  • A successful response means only that the sales channel accepted the update request. It does not confirm that the final state has been updated.

  • This operation is not idempotent. If the outcome is unclear, refresh get_order and the sales-channel order instead of retrying automatically. [Side effects] Replaces the existing tracking numbers of the selected sales-side items and may change their shipment or fulfillment status. [Confirmation] Always required. Before calling this Tool, show and confirm the exact store, order, sales-side items, new tracking numbers for each item, existing tracking numbers that will be replaced, and any possible shipment or fulfillment-status changes.

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": {
      "dsers_order_id": "<dsers_order_id>",
      "tracking_updates": "<tracking_updates>"
    },
    "name": "update_tracking_numbers_to_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
dsers_order_idYesExactly one DSers order ID. Copy from get_order. Required.
tracking_updatesYesNon-empty list of sales-side item tracking replacements. Each update targets exactly one items[].dsers_order_item_id. The complete tracking_numbers list replaces that item's existing numbers. Paste JSON example: [{"dsers_order_item_id":"2088507008557908225","tracking_numbers":["1Z999AA10123456784"]}].

Output Schema

NameRequiredDescriptionDefault
messageYesOutcome and safe next step
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The annotations already declare destructive, non-idempotent and open-world behavior, yet the description still adds real context: the replacement destroys existing tracking numbers, the sales channel may change shipment/fulfillment status, success only means the channel accepted the request, and automatic retries are unsafe. The mandatory confirmation step is spelled out as well, which no annotation conveys.

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?

Headers make it scannable and the critical fact (replacement, not append) is front-loaded and repeated at the point of use. It is longer than typical, with the replace-not-append rule appearing three times, which costs some efficiency on a mutation where redundancy is arguably deliberate.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, non-idempotent write with a nested array payload, the description covers prerequisites, validation, replacement semantics, side effects, response interpretation and confirmation — everything an agent needs to invoke it safely. The presence of an output schema means return-value detail need not be duplicated here.

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 100%, so the baseline is 3, but the description earns extra credit by warning that dsers_order_item_id must not be confused with supplier_order_item_id, requiring the same item ID to appear only once in tracking_updates, and stating that tracking numbers are trimmed and deduplicated with empties rejected — constraints absent from the schema itself.

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 names a specific verb and resource ("Adds or updates tracking numbers for selected sales-side order items") and pins down scope (sales-side only, replacement not append). It is clearly distinguishable from the sibling sync_existing_tracking_numbers_to_store, which is named explicitly.

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

Usage Guidelines5/5

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

It contains dedicated "When to use" and "When not to use" sections that name the alternatives and the condition that selects them: sync_existing_tracking_numbers_to_store for stored numbers, get_package_details for tracking events, and get_order as a mandatory prerequisite. It also states that appending is not supported, which removes the main wrong-turn an agent could take.

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.