Skip to main content
Glama

ADS Beast

create_webhook

Destructive

Register an endpoint ADS Beast calls when a chosen event happens. From then on those records go to that URL until it is removed. Without client_id it covers every client of the organization. Deliveries carry an HMAC in X-ADS-Beast-Signature and are retried; the generated secret is not returned, so pass secret_key if the receiver verifies signatures.

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": {
      "name": "<name>",
      "url": "<url>",
      "events": "<events>"
    },
    "name": "create_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http or https address of the receiving endpoint. Every matching event is sent to it.
nameYesLabel for the webhook in the ADS Beast interface.
eventsYesEvent names to subscribe to, for example ["lead.created"]. The available names come from list_webhook_events.
client_idNoLimit deliveries to one client's events. Omitted, the webhook receives every client's events in the organization.
secret_keyNoSigning secret for X-ADS-Beast-Signature, chosen by you. Omit to let ADS Beast generate one that this tool will not echo back.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, so the bar is lower, yet the description adds real operational context: deliveries carry an HMAC in X-ADS-Beast-Signature, failed deliveries are retried, and the generated secret is never echoed back. It does not explain the consequence implied by destructiveHint (persistent outbound traffic / removal obligation) in explicit terms, keeping it at 4.

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 tight sentences, front-loaded with what the tool creates and its lasting effect, then scope, then delivery mechanics. No filler and no repetition of the title.

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 5-parameter create tool with no output schema, it covers lifecycle, scoping, security, and retry behavior. Minor gaps remain: what is returned on success and whether duplicate webhooks for the same URL/event are permitted.

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 the baseline is 3; the description earns above that by explaining the decision behind secret_key (the generated secret is not returned, so supply your own if the receiver verifies signatures) and reinforcing the org-wide scope when client_id is omitted.

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 ('Register an endpoint ADS Beast calls when a chosen event happens') and immediately conveys the persistent effect ('those records go to that URL until it is removed'). An agent can tell this apart from sibling tools like list_webhook_events without opening either 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?

Gives conditional guidance on two decisions: omitting client_id scopes the webhook to the whole organization, and passing secret_key is warranted 'if the receiver verifies signatures.' No explicit when-not-to-use or named alternatives, so it falls short of a 5.

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.