Skip to main content
Glama
mattcoatsworth

ShipStation API MCP Server

create_label

Generate shipping labels for orders by providing label data in JSON format to streamline fulfillment processes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelDataYesJSON string containing the label data

Implementation Reference

  • Handler function for the 'create_label' MCP tool. Parses the labelData JSON string and delegates to shipStationClient.createLabel(), returning the result or error response.
    handler: async ({ labelData }) => {
      try {
        const parsedData = JSON.parse(labelData);
        const result = await shipStationClient.createLabel(parsedData);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: error.message }],
          isError: true
        };
      }
    }
  • Input schema for the create_label tool, defining labelData as a JSON string using Zod.
    schema: {
      labelData: z.string().describe("JSON string containing the label data")
    },
  • src/server.js:174-191 (registration)
    Registers all MCP tools including the 'create_label' tool from shipmentTools array by iterating and calling 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.createLabel method invoked by the tool handler, which sends a POST request to the ShipStation API endpoint '/shipments/createlabel'.
    async createLabel(data) {
      return this.request('POST', '/shipments/createlabel', 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