Skip to main content
Glama

delete_webhook

Remove a webhook from the ShipBob API to stop receiving automated notifications about fulfillment events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
webhookIdYesThe ID of the webhook to delete

Implementation Reference

  • Handler function that implements the core logic of the delete_webhook tool: deletes the specified webhook via the ShipBob API client and returns formatted success or error response.
    handler: async ({ webhookId }) => {
      try {
        await shipbobClient.deleteWebhook(webhookId);
        return {
          content: [{ 
            type: "text", 
            text: `Webhook deleted successfully`
          }]
        };
      } catch (error) {
        return {
          content: [{ type: "text", text: `Error deleting webhook: ${error.message}` }],
          isError: true
        };
      }
    }
  • Input schema validation using Zod for the delete_webhook tool, requiring a webhookId string.
    schema: {
      webhookId: z.string().describe("The ID of the webhook to delete")
    },
  • src/server.js:54-54 (registration)
    Registration call for the webhookTools array (containing delete_webhook tool) passed to registerTools function, which loops to call server.tool() for each tool on the MCP server.
    registerTools(webhookTools);
  • ShipBobClient helper method deleteWebhook(id) that performs the actual DELETE API request to ShipBob's /webhooks/{id} endpoint, invoked by the tool handler.
    async deleteWebhook(id) {
      return this.request('DELETE', `/webhooks/${id}`);
    }
  • Utility function registerTools that registers each tool in an array (including delete_webhook) to the MCP server.
    const registerTools = (toolsArray) => {
      toolsArray.forEach(tool => {
        server.tool(
          tool.name,
          tool.schema,
          tool.handler,
          { description: tool.description }
        );
      });
    };
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