Skip to main content
Glama
Pirate Ship MCP Server

Pirate Ship MCP Server

List import orders

list_import_orders
Read-onlyIdempotent

List imported unshipped store orders that still need shipping labels, including order number, recipient, items, and store; optionally show ignored orders.

Instructions

Unshipped orders from your connected store integrations, as in the Import grid.

Orders imported from connected stores that still need a label: one row per order with the grid's columns (order number, recipient, items, store). ignored true lists the orders you hid with ignore_orders. Run sync_store_orders first for the newest. Use order ids in create_batch_from_orders.

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_import_orders"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
ignoredNoShow the ignored orders instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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."
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds genuinely new behavior: that results are unfiltered-by-user order rows including hidden orders via the ignored flag, and that data freshness depends on sync_store_orders. It does not mention paging/return envelope, but offset's schema text covers the total.

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?

Four short sentences, each carrying distinct information (scope, row shape, ignored variant, prerequisite, next step), with the primary scope front-loaded. Density is high but nothing is redundant; the 'as in the Import grid' analogy earns its place by anchoring the column set.

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 no output schema, the description does the work of describing returns ('one row per order with the grid's columns: order number, recipient, items, store'). Combined with the pagination detail in the schema, an agent has enough to call it correctly; only the total-count semantics of paging are left implicit.

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, but the description adds meaning beyond the schema for `ignored` — explaining that these are orders hidden via ignore_orders, not a different dataset. It does not elaborate on limit/offset/search beyond the grid analogy, so it stays modestly above baseline rather than full marks.

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?

The description names the exact resource ('unshipped orders from connected store integrations') and states the row shape ('one row per order with the grid's columns'), which separates it from shipment, batch, and recipient listing siblings. It lacks an explicit verb opening ('List…'), relying on the tool name for that, but the scope is unambiguous.

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?

It gives concrete sequencing ('Run sync_store_orders first for the newest') and a downstream consumer ('Use order ids in create_batch_from_orders'), plus routes the 'ignored' case to the ignore_orders tool. No explicit when-not-to-use case is stated, but the operational context is clear.

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