Skip to main content
Glama
Upload-Post

Upload-Post

Official

Delete a webhook subscription

delete_webhook_subscription
DestructiveIdempotent

Delete a webhook subscription to stop Upload-Post from sending events to that endpoint immediately while leaving the account webhook and other subscriptions intact.

Instructions

Delete a webhook subscription: Upload-Post stops sending to it right away. The account webhook and other subscriptions are not touched. A second delete answers 404 not_found. Not generally available yet: until webhook subscriptions are switched on for the account, every call answers 503 with reason webhook_subscriptions_disabled (the feature is off, not a temporary failure). Needs the user's approval: call it first without confirmed to get a preview (nothing is sent), show the user exactly what will go out, and repeat the call with confirmed: true only after they approve.

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": {
      "subscription_id": "<subscription_id>"
    },
    "name": "delete_webhook_subscription"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmedNoSet to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.
subscription_idYesSubscription id (`whsub_...`) from list_webhook_subscriptions or create_webhook_subscription.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.26.5

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true and readOnly=false, but the description adds real context the annotations cannot: deletion is immediate, collateral webhooks are unaffected, repeat deletes return 404 not_found, and the feature may be globally disabled with a 503 plus a specific reason code. The only mild tension is that a 404 on repeat calls is framed as expected despite idempotentHint=true — the underlying state is unchanged, so this reads as clarification rather than contradiction.

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?

Purpose and blast radius are front-loaded, and every sentence carries new information (preview flow, 404 semantics, 503 feature gate). The semicolon-packed density makes it slightly harder to scan than a bulleted breakdown would be, but there is no filler.

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, feature-gated mutation with an output schema already present, the description covers everything an agent needs: effect scope, approval protocol, expected failure modes and their reason codes. Nothing material is left to inference.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds meaning by framing `confirmed` as part of an approval protocol ('call it first without `confirmed` to get a preview (nothing is sent)') rather than a bare boolean flag. The `subscription_id` provenance is left to the schema's own description, which already names list/create siblings.

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 first sentence states a specific verb and resource ('Delete a webhook subscription') and immediately scopes the effect ('Upload-Post stops sending to it right away'). It also bounds the blast radius ('The account webhook and other subscriptions are not touched'), which separates it from other delete_* siblings in the catalog without naming them.

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?

It gives an explicit two-step protocol — call without `confirmed` for a preview, show the user, then repeat with `confirmed: true` — plus the conditions under which a call fails (404 on a second delete, 503 while the feature is off). It even pre-empts the misreading of the 503 as a transient error.

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