Skip to main content
Glama
mattcoatsworth

ShipStation API MCP Server

list_orders

Retrieve and filter orders from ShipStation with pagination, sorting, and date-based criteria to manage order data efficiently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
pageSizeNoNumber of orders per page (max 500)
sortByNoSort orders by a specific field
sortDirNoSort direction
orderStatusNoFilter by order status
storeIdNoFilter by store ID
createDateStartNoFilter by creation date (start)
createDateEndNoFilter by creation date (end)
modifyDateStartNoFilter by modification date (start)
modifyDateEndNoFilter by modification date (end)

Implementation Reference

  • Handler function that executes the list_orders tool by calling shipStationClient.getOrders and formatting the response.
    handler: async (params) => {
      try {
        const orders = await shipStationClient.getOrders(params);
        return {
          content: [{ type: "text", text: JSON.stringify(orders, null, 2) }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: error.message }],
          isError: true
        };
      }
    }
  • Zod schema defining the input parameters for filtering, sorting, and paginating the list_orders tool.
    schema: {
      page: z.number().optional().describe("Page number"),
      pageSize: z.number().optional().describe("Number of orders per page (max 500)"),
      sortBy: z.string().optional().describe("Sort orders by a specific field"),
      sortDir: z.enum(["ASC", "DESC"]).optional().describe("Sort direction"),
      orderStatus: z.string().optional().describe("Filter by order status"),
      storeId: z.number().optional().describe("Filter by store ID"),
      createDateStart: z.string().optional().describe("Filter by creation date (start)"),
      createDateEnd: z.string().optional().describe("Filter by creation date (end)"),
      modifyDateStart: z.string().optional().describe("Filter by modification date (start)"),
      modifyDateEnd: z.string().optional().describe("Filter by modification date (end)")
    },
  • src/server.js:174-191 (registration)
    Bulk registration of all tools including list_orders (from orderTools) to the MCP server via server.tool().
    [
      ...orderTools,
      ...shipmentTools,
      ...carrierTools,
      ...warehouseTools,
      ...productTools,
      ...customerTools,
      ...storeTools,
      ...webhookTools,
      ...fulfillmentTools
    ].forEach(tool => {
      server.tool(
        tool.name,
        tool.schema,
        tool.handler,
        { description: tool.description }
      );
    });
  • ShipStationClient.getOrders method used by the handler to make the actual API request to list orders.
    async getOrders(params) {
      return this.request('GET', '/orders', null, params);
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mattcoatsworth/shipstation-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server