Skip to main content
Glama
mattcoatsworth

ShipStation API MCP Server

get_shipment

Retrieve shipment details by ID from the ShipStation API to track order fulfillment status and shipping information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shipmentIdYesShipment ID to retrieve

Implementation Reference

  • The handler function for the 'get_shipment' tool. It takes a shipmentId parameter, fetches the shipment details using shipStationClient.getShipment, stringifies the result to JSON, and returns it in the expected MCP format, or returns an error message if the call fails.
    handler: async ({ shipmentId }) => {
      try {
        const shipment = await shipStationClient.getShipment(shipmentId);
        return {
          content: [{ type: "text", text: JSON.stringify(shipment, null, 2) }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: error.message }],
          isError: true
        };
      }
    }
  • Zod input schema for the 'get_shipment' tool, defining the required shipmentId as a number.
    schema: {
      shipmentId: z.number().describe("Shipment ID to retrieve")
    },
  • The complete 'get_shipment' tool object definition, which is part of the shipmentTools array exported and later spread into the MCP server's tool registration.
    {
      name: "get_shipment",
      description: "Get details for a specific shipment",
      schema: {
        shipmentId: z.number().describe("Shipment ID to retrieve")
      },
      handler: async ({ shipmentId }) => {
        try {
          const shipment = await shipStationClient.getShipment(shipmentId);
          return {
            content: [{ type: "text", text: JSON.stringify(shipment, null, 2) }]
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: error.message }],
            isError: true
          };
        }
      }
    },
  • src/server.js:174-191 (registration)
    Generic MCP server tool registration code that spreads all tool arrays (including shipmentTools which contains get_shipment) and registers each tool using server.tool().
    [
      ...orderTools,
      ...shipmentTools,
      ...carrierTools,
      ...warehouseTools,
      ...productTools,
      ...customerTools,
      ...storeTools,
      ...webhookTools,
      ...fulfillmentTools
    ].forEach(tool => {
      server.tool(
        tool.name,
        tool.schema,
        tool.handler,
        { description: tool.description }
      );
    });
  • API client helper method getShipment used by the tool handler to make the actual HTTP GET request to ShipStation's /shipments/{shipmentId} endpoint.
    async getShipment(shipmentId) {
      return this.request('GET', `/shipments/${shipmentId}`);
    }
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