Skip to main content
Glama

webhooks_delete

Delete a webhook by its ID to permanently remove it and stop all notifications. Use for cleaning up invalid endpoints or decommissioned integrations.

Instructions

Delete a webhook by its ID.

Permanently removes a webhook from Pipedrive. Once deleted, the webhook will no longer send notifications to the subscription URL.

When to delete webhooks:

  • The endpoint URL is no longer valid or in use

  • You want to stop receiving notifications for specific events

  • You're cleaning up test/development webhooks

  • The integration using the webhook has been decommissioned

  • The webhook is failing consistently and needs to be recreated

Workflow:

  1. Use webhooks/list to get the ID of the webhook you want to delete

  2. Call webhooks/delete with the webhook ID

  3. Confirm deletion was successful

Important notes:

  • This action is permanent and cannot be undone

  • Deleting a webhook will immediately stop all notifications

  • You can recreate a webhook with the same settings later if needed

  • Use webhooks/list after deletion to verify it was removed

Example:

  • Delete webhook: { "id": 123 }

Best practices:

  • Always verify the webhook ID before deletion

  • Document which webhooks are deleted and why

  • Consider disabling temporarily instead if you might need it again

  • Keep track of webhook configurations for recreating if needed

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the webhook to delete (required)
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. It states the action is permanent, immediately stops notifications, cannot be undone, and that webhooks can be recreated. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with sections and front-loaded summary. Slightly long but each section adds value. Not overly verbose for the complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a simple delete tool with one parameter and no output schema. Covers purpose, use cases, workflow, notes, and best practices thoroughly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter 'id' with schema description 'ID of the webhook to delete (required)'. Description adds no extra meaning beyond schema; baseline 3 due to 100% schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Delete a webhook by its ID. Permanently removes a webhook from Pipedrive.' This provides a specific verb and resource, and among sibling tools (webhooks_create, webhooks_list), it is distinctively deletion-focused.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly lists when to delete (endpoint invalid, stop notifications, cleanup, etc.), provides a workflow referencing webhooks/list, and advises on verification. It also contrasts with creation and listing tools implicitly.

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/iamsamuelfraga/mcp-pipedrive'

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