Skip to main content
Glama
tribeunal

Tribeunal Decision-Making Platform

Official
by tribeunal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete webhook

tribeunal_delete_webhook
Destructive

Permanently delete a webhook endpoint to immediately stop deliveries and destroy its signing secret. For temporary pauses or event changes, update the existing webhook instead.

Instructions

Permanently delete one of your webhook endpoints; deliveries stop immediately and the signing secret is destroyed — irreversible. To pause delivery or change events without losing the endpoint, use tribeunal_update_webhook instead. Re-registering the same URL with tribeunal_create_webhook issues a brand-new secret, so a receiver still configured with the old one fails signature verification. An endpoint you don't own answers 404 webhook_not_found, same as an unknown one. The API answers 204 No Content — the tool confirms deletion by naming the uuid, not a JSON object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
webhookIdYesEndpoint UUID, from tribeunal_list_webhooks or the tribeunal_create_webhook response. An endpoint you don't own, or an unknown uuid, both answer 404 webhook_not_found.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / properties / webhookId / description
      Previous value: -"Webhook endpoint UUID to delete"New value: +"Endpoint UUID, from tribeunal_list_webhooks or the tribeunal_create_webhook response. An endpoint you don't own, or an unknown uuid, both answer 404 webhook_not_found."
  2. First observedv1.13.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description adds critical behavioral context: deliveries stop immediately, the signing secret is destroyed, the operation is irreversible, non-owned endpoints return 404, and the API returns 204 with confirmation via uuid rather than a JSON object. This fully discloses the side effects and response semantics beyond what annotations convey.

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?

Every sentence earns its place: the irreversible effect is front-loaded, alternatives and failure modes are concisely covered, and the response format is clarified. No fluff, well-ordered, and compact for the information density.

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 destructive tool with no output schema, the description covers all essential operational aspects: immediate consequences, alternative non-destructive path, re-registration pitfall, 404 semantics, and how the tool confirms success. An agent has everything needed to call it correctly and safely.

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 description coverage is 100% and the parameter's schema description already explains the uuid pattern, its source, and the 404 behavior for unowned/unknown uuids. The tool description adds no new parameter-level information beyond what the schema provides, so the baseline of 3 is appropriate.

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?

States a specific verb ('delete') and resource ('webhook endpoint') with precise scope ('one of your'), and distinguishes itself from update and create siblings. The irreversible consequence is front and center, leaving no ambiguity about what this tool does.

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 names the alternative (tribeunal_update_webhook) and the exact condition that should route to it (pausing delivery or changing events without losing the endpoint). Also explains the consequence of re-registering via create, which helps the agent avoid a common mistake.

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

Deploy Server

Other Tools