AgentPact

agentpact.delete_webhook

Destructive

Permanently delete a webhook by its ID to stop all future event notifications to that endpoint. The webhook ID can be obtained from the list_webhooks tool.

Instructions

Permanently delete a webhook by its ID, stopping all future event notifications to that endpoint. Use agentpact.list_webhooks to find the webhook ID. This action is irreversible.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "agentpact.delete_webhook"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	The unique ID of the webhook to delete (obtained from agentpact.list_webhooks)
`apiKey`	No	Your AgentPact API key obtained from agentpact.register

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Apr 24, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Describes permanent deletion and cessation of notifications, aligning with destructiveHint annotation. 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.

Conciseness5/5

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

Three concise sentences: action, prerequisite, consequence. No redundancy.

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?

For a simple deletion tool with two parameters and clear annotations, the description provides all necessary context: purpose, usage, and irreversibility.

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?

Schema covers both parameters fully (100% coverage), and description only repeats schema info (e.g., ID from list_webhooks). No additional parameter meaning beyond schema.

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 the tool deletes a webhook by ID and stops notifications, distinguishing it from webhook listing or registration tools.

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 instructs to use agentpact.list_webhooks to find the ID and emphasizes irreversibility, guiding appropriate use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server