Delete a webhook push subscription
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": "deletePushSubscription"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure, yet it says nothing about irreversibility, whether the record can be restored, what happens if the id does not exist, or what the call returns. For a destructive mutation with zero annotation coverage this is a major gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single five-word phrase with no padding and the resource stated up front. It is efficient, though the brevity comes at the cost of the behavioral and parameter detail the tool needs.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
A destructive single-parameter tool with no annotations and no output schema needs the description to supply irreversibility, auth/permission needs, and the id's provenance. None of that is present, leaving the definition inadequate for safe invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0% and the single parameter 'id' is completely untyped in prose — the description does not say whether it is the subscription id, a webhook id, or a channel identifier. An agent must infer the identifier's origin, and nothing indicates whether it can be obtained from listPushSubscriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb ('Delete') plus specific resource ('webhook push subscription') tells an agent exactly what the tool does and separates it from createPushSubscription, listPushSubscriptions and togglePushSubscription. It stops short of stating how it differs from togglePushSubscription, which also changes subscription state, so it is clear but not fully differentiated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no statement of when to use this versus togglePushSubscription (which may deactivate rather than remove) or listPushSubscriptions for discovery. No preconditions, no note about needing a valid id obtained elsewhere.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.