Skip to main content
Glama
mattcoatsworth

ShipStation API MCP Server

mark_order_as_shipped

Update order status to shipped in ShipStation by providing carrier details, ship date, and tracking number for shipment confirmation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderIdYesOrder ID to mark as shipped
carrierCodeYesCarrier code
shipDateYesShip date (YYYY-MM-DD)
trackingNumberYesTracking number

Implementation Reference

  • The MCP tool handler for 'mark_order_as_shipped'. Destructures input params, calls shipStationClient.markOrderAsShipped, formats result as MCP content or error.
    handler: async ({ orderId, carrierCode, shipDate, trackingNumber }) => {
      try {
        const result = await shipStationClient.markOrderAsShipped({
          orderId,
          carrierCode,
          shipDate,
          trackingNumber
        });
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: error.message }],
          isError: true
        };
      }
    }
  • Zod input schema defining required parameters for the mark_order_as_shipped tool.
    schema: {
      orderId: z.number().describe("Order ID to mark as shipped"),
      carrierCode: z.string().describe("Carrier code"),
      shipDate: z.string().describe("Ship date (YYYY-MM-DD)"),
      trackingNumber: z.string().describe("Tracking number")
    },
  • src/server.js:184-191 (registration)
    Registration loop in MCP server that registers the mark_order_as_shipped tool (included via ...orderTools) using server.tool().
    ].forEach(tool => {
      server.tool(
        tool.name,
        tool.schema,
        tool.handler,
        { description: tool.description }
      );
    });
  • ShipStationClient helper method that performs the actual API POST request to mark an order as shipped.
    async markOrderAsShipped(data) {
      return this.request('POST', '/orders/markasshipped', data);
    }
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