Skip to main content
Glama

create_return

Create a return for a ShipBob order by specifying order ID, items to return, and return address information to process customer returns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderIdYesThe ID of the order to create a return for
itemsYesItems to return
returnAddressNoReturn address information

Implementation Reference

  • The handler function implementing the 'create_return' MCP tool logic. It calls the ShipBob API client to create the return and formats a text response with the result or error.
    handler: async (returnData) => {
      try {
        const newReturn = await shipbobClient.createReturn(returnData);
        return {
          content: [{ 
            type: "text", 
            text: `Return created successfully: ${JSON.stringify(newReturn, null, 2)}`
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error creating return: ${error.message}` }],
          isError: true
        };
      }
    }
  • Zod schema defining the input parameters for the 'create_return' tool: orderId, items (array of orderItemId, quantity, optional reason), and optional returnAddress object.
    schema: {
      orderId: z.string().describe("The ID of the order to create a return for"),
      items: z.array(
        z.object({
          orderItemId: z.string().describe("Order item ID to return"),
          quantity: z.number().describe("Quantity to return"),
          reason: z.string().optional().describe("Reason for return")
        })
      ).describe("Items to return"),
      returnAddress: z.object({
        name: z.string().describe("Return address name"),
        address1: z.string().describe("Address line 1"),
        address2: z.string().optional().describe("Address line 2"),
        city: z.string().describe("City"),
        state: z.string().describe("State/Province"),
        zipCode: z.string().describe("Zip/Postal code"),
        country: z.string().describe("Country code (e.g., US)")
      }).optional().describe("Return address information")
    },
  • src/server.js:55-55 (registration)
    Registers the returnTools array (which includes the 'create_return' tool) with the MCP server using the generic registerTools function.
    registerTools(returnTools);
  • ShipBobClient helper method that makes the POST request to '/returns' endpoint, invoked by the tool handler.
    async createReturn(returnData) {
      return this.request('POST', '/returns', returnData);
    }
  • The tool specification object for 'create_return' defined in the returnTools array, which is later registered with the MCP server.
    {
      name: "create_return",
      description: "Create a new return in ShipBob",
      schema: {
        orderId: z.string().describe("The ID of the order to create a return for"),
        items: z.array(
          z.object({
            orderItemId: z.string().describe("Order item ID to return"),
            quantity: z.number().describe("Quantity to return"),
            reason: z.string().optional().describe("Reason for return")
          })
        ).describe("Items to return"),
        returnAddress: z.object({
          name: z.string().describe("Return address name"),
          address1: z.string().describe("Address line 1"),
          address2: z.string().optional().describe("Address line 2"),
          city: z.string().describe("City"),
          state: z.string().describe("State/Province"),
          zipCode: z.string().describe("Zip/Postal code"),
          country: z.string().describe("Country code (e.g., US)")
        }).optional().describe("Return address information")
      },
      handler: async (returnData) => {
        try {
          const newReturn = await shipbobClient.createReturn(returnData);
          return {
            content: [{ 
              type: "text", 
              text: `Return created successfully: ${JSON.stringify(newReturn, null, 2)}`
            }]
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Error creating return: ${error.message}` }],
            isError: true
          };
        }
      }
    }
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