Skip to main content
Glama

Unsubscribe a Network webhook

unsubscribe_network_webhook

Remove a key owner's webhook subscription to stop event notifications. Deletes the specified subscription from the network list.

Instructions

Remove one of this key owner's webhook subscriptions (from list_network_subscriptions). Needs a write-scope API key.

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": "unsubscribe_network_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSubscription id (publicId)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description still discloses the key behavioral facts an agent needs: this is a destructive removal scoped to the key owner and it requires write-scope auth. It does not say whether removal is reversible, what happens if the id is unknown or belongs to another owner, or what is returned.

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?

Two short sentences, action first, prerequisite second, with no redundant wording.

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

Completeness4/5

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

For a one-parameter destructive tool with no output schema, the description covers what it does, where the id comes from, and the auth requirement. Missing only edge-case behavior (unknown id, ownership mismatch) that would bring it to a 5.

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 coverage is 100% and the single parameter is fully documented as the subscription publicId. The description adds only the provenance hint (ids come from list_network_subscriptions), which is mildly useful but not additional semantics about format or validity.

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 and resource ("Remove one of this key owner's webhook subscriptions") and ties it to the listing tool that produces the id, so an agent can distinguish it from subscribe/list siblings without opening the schema.

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

Usage Guidelines4/5

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

Clear context: use this to remove a subscription previously obtained from list_network_subscriptions, plus the prerequisite of a write-scope API key. No explicit exclusion or mention of the paired subscribe_network_webhook, so it stops short of full when/when-not guidance.

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