Skip to main content
Glama

create_shipment

Create a shipment for an order by specifying items, shipping method, and optional fulfillment center to initiate fulfillment through ShipBob's API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderIdYesThe ID of the order to create a shipment for
fulfillmentCenterIdNoPreferred fulfillment center ID
shippingMethodYesShipping method to use
itemsYesItems to ship

Implementation Reference

  • MCP tool handler for 'create_shipment' that calls the ShipBob API client to create a new shipment and returns success or error response.
    handler: async (shipmentData) => {
      try {
        const newShipment = await shipbobClient.createShipment(shipmentData);
        return {
          content: [{ 
            type: "text", 
            text: `Shipment created successfully: ${JSON.stringify(newShipment, null, 2)}`
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error creating shipment: ${error.message}` }],
          isError: true
        };
      }
    }
  • Zod schema defining the input parameters for the create_shipment tool: orderId, optional fulfillmentCenterId, shippingMethod, and items array.
    schema: {
      orderId: z.string().describe("The ID of the order to create a shipment for"),
      fulfillmentCenterId: z.string().optional().describe("Preferred fulfillment center ID"),
      shippingMethod: z.string().describe("Shipping method to use"),
      items: z.array(
        z.object({
          orderItemId: z.string().describe("Order item ID to ship"),
          quantity: z.number().describe("Quantity to ship")
        })
      ).describe("Items to ship")
    },
  • src/server.js:23-32 (registration)
    Utility function to register MCP tools from arrays like fulfillmentTools, which contains create_shipment. Called at line 53 for fulfillmentTools.
    const registerTools = (toolsArray) => {
      toolsArray.forEach(tool => {
        server.tool(
          tool.name,
          tool.schema,
          tool.handler,
          { description: tool.description }
        );
      });
    };
  • src/server.js:53-53 (registration)
    Specific registration call for fulfillmentTools array, which includes the create_shipment tool.
    registerTools(fulfillmentTools);
  • ShipBobClient helper method invoked by the tool handler to perform the actual POST request to the ShipBob /shipments API endpoint.
    async createShipment(shipmentData) {
      return this.request('POST', '/shipments', shipmentData);
    }
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/shipbob-mcp-server'

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