starshipit-mcp

Create Tracking Order

starshipit_create_tracking_order

Create tracking-only orders in StarShipIt for shipments dispatched outside the platform, enabling centralized tracking, notifications, and reporting for carrier-booked parcels.

Instructions

Create tracking-only orders in StarShipIt for shipments dispatched outside the platform.

When to use: Use this tool when you have shipments that were booked or dispatched through a carrier directly (not via StarShipIt) and you want to import them into StarShipIt to enable centralised tracking, notifications, and reporting. At least one of name or order_number should be provided per order entry.

Parameters:

orders (required): Array of tracking order objects to create. Each object requires:
- carrier (required): Carrier code for the shipment (e.g. "AUSPOST", "DHL", "UPS").
- tracking_number (required): The carrier-assigned tracking number (e.g. "1Z999AA10123456784").
- name (optional but recommended): Recipient or customer name associated with the shipment.
- order_number (optional but recommended): Your internal order/reference number.

Note: At least one of name or order_number must be supplied per entry to make tracking orders identifiable in the StarShipIt dashboard.

Returns: An array of created order records, each with the new StarShipIt order ID, order number, tracking number, and carrier. Individual entries that fail will include an error field.

Example success response:

{
  "success": true,
  "orders": [
    {
      "order_id": 55001,
      "order_number": "ORD-9901",
      "tracking_number": "1Z999AA10123456784",
      "carrier": "UPS"
    },
    {
      "order_id": 55002,
      "order_number": "ORD-9902",
      "tracking_number": "EJ123456789AU",
      "carrier": "AUSPOST"
    }
  ]
}

Error cases: 400 if carrier or tracking_number is missing for any entry; 409 if a tracking number already exists in the platform.

Input Schema

Name	Required	Description	Default
`orders`	Yes	Array of tracking orders to create. Each must have carrier and tracking_number; supply name or order_number for identification.

Output Schema

Name	Required	Description
`errors`	No	Validation or processing errors returned by StarShipIt
`object`	No	The response payload when StarShipIt returns a non-object value
`success`	No	StarShipIt success flag (a boolean on most endpoints)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 3, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, openWorldHint=true), the description adds real behavioral detail: partial-failure semantics (failed entries carry an `error` field rather than failing the whole batch), 400 for missing carrier/tracking_number, and 409 for duplicate tracking numbers. That duplicate-tracking error also makes the non-idempotent hint concrete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Heading-based structure is front-loaded and easy to scan, but the "Parameters" section reproduces the schema verbatim and the full example success response is redundant given the tool has an output schema. Roughly a third of the text earns no new information.

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 single-parameter batch-creation tool, nothing an agent needs is missing: scope, entry requirements, per-entry failure handling, error codes, and return shape are all covered, and the output schema plus example remove remaining ambiguity.

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; the description adds the cross-field identifiability rule (at least one of `name` or `order_number` per entry, repeated twice as a hard note) and concrete carrier/tracking examples. It largely restates the schema's own per-field descriptions, so the gain over structured data is modest rather than substantial.

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?

States a specific verb and resource ("Create tracking-only orders") and immediately bounds the scope to "shipments dispatched outside the platform", which distinguishes it from the sibling create_order / create_orders_bulk tools that create fulfillment orders. An agent can classify the tool without opening the schema.

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?

The explicit "When to use" block gives a clear entry condition: shipments booked or dispatched directly through a carrier, not via StarShipIt, that need centralised tracking. It stops short of naming the sibling alternative (create_order) to route away from, so the exclusion is implied rather than explicit.

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

Deploy Server