Skip to main content
Glama
mattcoatsworth

ShipStation API MCP Server

get_customer

Retrieve customer details from ShipStation using a customer ID to access shipping information and manage order data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerIdYesCustomer ID to retrieve

Implementation Reference

  • The async handler function for the 'get_customer' tool. It retrieves the customer using shipStationClient.getCustomer(customerId), returns JSON-formatted response or error message.
    handler: async ({ customerId }) => {
      try {
        const customer = await shipStationClient.getCustomer(customerId);
        return {
          content: [{ type: "text", text: JSON.stringify(customer, null, 2) }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: error.message }],
          isError: true
        };
      }
    }
  • Zod schema defining the required input parameter 'customerId' as a number.
    schema: {
      customerId: z.number().describe("Customer ID to retrieve")
    },
  • src/server.js:174-191 (registration)
    The registration loop that spreads customerTools (containing 'get_customer') and registers each tool with the MCP server 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 }
      );
    });
  • ShipStationClient method getCustomer that makes the API request to retrieve a specific customer, called by the tool handler.
    async getCustomer(customerId) {
      return this.request('GET', `/customers/${customerId}`);
    }
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