Skip to main content
Glama

create_webhook

Set up webhook notifications for ShipBob API events like order.created or shipment.created to receive automated updates at your specified URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to send webhook notifications to
eventTypeYesEvent type to subscribe to (e.g., 'order.created', 'shipment.created')
isActiveNoWhether the webhook is active

Implementation Reference

  • The main handler function for the create_webhook tool. It processes the input parameters, calls the ShipBob API client to create the webhook, and returns a formatted response or error message.
    handler: async ({ url, eventType, isActive = true }) => {
      try {
        const webhookData = {
          url,
          eventType,
          isActive
        };
        const newWebhook = await shipbobClient.createWebhook(webhookData);
        return {
          content: [{ 
            type: "text", 
            text: `Webhook created successfully: ${JSON.stringify(newWebhook, null, 2)}`
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error creating webhook: ${error.message}` }],
          isError: true
        };
      }
    }
  • Zod schema defining the input parameters for the create_webhook tool: required URL (validated as URL), eventType (string), and optional isActive (boolean).
    schema: {
      url: z.string().url().describe("The URL to send webhook notifications to"),
      eventType: z.string().describe("Event type to subscribe to (e.g., 'order.created', 'shipment.created')"),
      isActive: z.boolean().optional().describe("Whether the webhook is active")
    },
  • src/server.js:54-54 (registration)
    Registers the webhookTools array, which includes the create_webhook tool, with the MCP server using the registerTools utility function.
    registerTools(webhookTools);
  • Helper method in the ShipBobClient class that makes the actual API POST request to create a webhook.
    async createWebhook(webhookData) {
      return this.request('POST', '/webhooks', webhookData);
    }
  • The tool definition object within the webhookTools array, including name, description, schema, and handler for create_webhook.
    {
      name: "create_webhook",
      description: "Create a new webhook in ShipBob",
      schema: {
        url: z.string().url().describe("The URL to send webhook notifications to"),
        eventType: z.string().describe("Event type to subscribe to (e.g., 'order.created', 'shipment.created')"),
        isActive: z.boolean().optional().describe("Whether the webhook is active")
      },
      handler: async ({ url, eventType, isActive = true }) => {
        try {
          const webhookData = {
            url,
            eventType,
            isActive
          };
          const newWebhook = await shipbobClient.createWebhook(webhookData);
          return {
            content: [{ 
              type: "text", 
              text: `Webhook created successfully: ${JSON.stringify(newWebhook, null, 2)}`
            }]
          };
        } catch (error) {
          return {
            content: [{ type: "text", text: `Error creating webhook: ${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