Skip to main content
Glama
Pirate Ship MCP Server

Pirate Ship MCP Server

List shipments

list_shipments
Read-onlyIdempotent

Retrieve purchased Pirate Ship labels with recipient, carrier, tracking, cost and status, newest first. Filter by search, date range, status, carrier or batch and page through results.

Instructions

Labels bought in Pirate Ship with recipient, tracking, cost and status, newest first.

The Reports, Shipments table: every label the account bought, with the recipient's address, carrier and service, tracking number and status, cost in US dollars, package size and weight, batch and ship-from address. search works like the table's search box (name, email, tracking number, order id). from_date and to_date narrow by the day the label was created; status, tracking_status, carrier and batch take the values the table shows. total counts every match, limit and offset page through them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_shipments"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoOrder by date.newest
batchNoBatch titles.
limitNoRows per page, 1 to 100.
offsetNoRows to skip: the next page starts at offset + limit while it is below total.
searchNoFree text, as in the report's search box.
statusNoLabel status as the report shows it, e.g. Printed, Refunded.
carrierNoUSPS or UPS.
to_dateNoLast day, YYYY-MM-DD, included.
from_dateNoFirst day, YYYY-MM-DD, in your timezone.
tracking_statusNoTracking status as the report shows it, e.g. Delivered, In Transit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.4
    • addedInput schema / properties / limit / description
      Added value: +"Rows per page, 1 to 100."
    • addedInput schema / properties / offset / description
      Added value: +"Rows to skip: the next page starts at offset + limit while it is below total."
    • addedInput schema / properties / sort / description
      Added value: +"Order by date."
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: default newest-first ordering, the exact shape of each row, and that 'total counts every match' while limit/offset page through it — useful for an agent planning pagination loops.

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?

Front-loaded with the resource and its fields, then filters, then pagination — a logical order with no filler sentences. Slight redundancy with the schema (limit/offset paging is restated from the offset description) keeps it from a 5.

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?

With 10 optional parameters and no output schema, the description carries the necessary weight by enumerating the returned columns and explaining how total/limit/offset interact. Complete enough to invoke correctly; it only lacks guidance on result-set size or behavior when no labels match.

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 baseline is 3, and the description earns above baseline by clarifying that search matches name, email, tracking number, and order id, and that status/tracking_status/carrier/batch take the same values shown in the report table. It stops at 4 because it adds nothing on sort, and date semantics overlap with the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource framing ('Labels bought in Pirate Ship with recipient, tracking, cost and status, newest first') and enumerates the returned fields, so the agent knows this is a paginated list of purchased labels, not a single-record fetch. It does not explicitly distinguish itself from close siblings like export_shipments, list_return_labels, or get_shipment, so it stops short of a 5.

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

Usage Guidelines3/5

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

The description explains how each filter behaves ('search works like the table's search box', date filters 'narrow by the day the label was created'), which implies when to reach for it — querying the Reports/Shipments table. But it never states when to prefer export_shipments or get_shipment instead, and gives no exclusions or prerequisites.

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