Transistor-MCP

unsubscribe_webhook

Remove a webhook subscription by providing its ID to stop receiving notifications from Transistor.fm.

Instructions

Unsubscribe from a webhook

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": {
      "webhook_id": "<webhook_id>"
    },
    "name": "unsubscribe_webhook"
  }
}

Input Schema

Name	Required	Description	Default
`webhook_id`	Yes	ID of the webhook to unsubscribe from

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 25, 2026

TDQS

C2.7/5.0

Behavior1/5

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

With no annotations, the description lacks any disclosure of behavioral traits such as side effects, permissions required, or confirmation of unsubscription. The minimal text does not inform the agent about what happens after invoking the tool.

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?

The description is a single sentence with no superfluous words, making it extremely concise and easy to parse.

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

Completeness2/5

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

Despite the tool's simplicity, the description provides no context about prerequisites, confirmations, or relationship to other webhook tools. A simple operation may still need context about its effects.

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?

The input schema already covers 100% of parameter descriptions, so the description adds no additional meaning. Baseline score of 3 is appropriate.

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

Purpose4/5

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

The description clearly states the action (unsubscribe) and resource (webhook), providing basic purpose clarity. However, it does not differentiate from the sibling 'subscribe_webhook' tool, missing an opportunity for distinction.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'subscribe_webhook' or 'list_webhooks'. The agent receives no context about prerequisites or appropriate usage scenarios.

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