Skip to main content
Glama

Revoke Event Webhook

revoke_event_webhook
Destructive

Disable an event webhook. Stops future deliveries and retries; an already in-flight HTTP request may finish. Requires event host access and a write 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": {
      "event_id": "<event_id>",
      "webhook_id": "<webhook_id>"
    },
    "name": "revoke_event_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYes
webhook_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior5/5

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

The description adds substantial context beyond the annotations: it explains that future deliveries and retries stop while an in-flight HTTP request may still complete, and it discloses the required event host access and write key. These are meaningful behavioral and authorization details not captured by destructiveHint or idempotentHint.

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?

Three short sentences, front-loaded with the action, followed by delivery semantics and access requirements. Every sentence adds distinct value with no filler.

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

Completeness3/5

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

The description is strong on mutation behavior, in-flight request handling, and authorization requirements, but it omits any explanation of the two required identifiers despite the tool having no output schema and 0% parameter description coverage. For a destructive tool, that leaves a meaningful gap in invocation clarity.

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

Parameters1/5

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

Schema description coverage is 0% for both required parameters, and the description does not mention event_id or webhook_id at all. With no compensating explanation of what each identifier selects or the expected webhook_id format, the agent gets no semantic help beyond the raw schema.

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: 'Disable an event webhook.' This clearly distinguishes the operation from siblings such as create_event_webhook, list_event_webhooks, and replay_webhook_delivery without ambiguity.

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

Usage Guidelines3/5

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

The implied use case is clear from 'Disable an event webhook,' but there is no explicit when-to-use guidance, no when-not-to-use exclusions, and no named alternative such as replay_webhook_delivery or list_webhook_deliveries for related tasks.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.