kualat-mcp

Create a webhook

create_webhook

Subscribe a public HTTP endpoint to link events, receive the webhook signing secret, and get HMAC-SHA256-signed deliveries for link changes and clicks.

Instructions

Subscribe an endpoint to link events. The response carries the signing secret (whsec_); deliveries follow the Standard Webhooks spec, signed with HMAC-SHA256 over "{id}.{timestamp}.{payload}".

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

Input Schema

Name	Required	Description
`url`	Yes	Public http or https endpoint that receives the POST.
`name`	No	Label to recognise the subscription by.
`events`	Yes	Events to receive.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world operation, so the bar is lower, and the description still adds real value: the response carries a whsec_ signing secret and deliveries follow Standard Webhooks with HMAC-SHA256 over "{id}.{timestamp}.{payload}". It omits whether the secret is shown only once and any retry/failure semantics, so it falls just short of exhaustive.

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 sentences, front-loaded with the core action, then the response contract and signature scheme. Every clause conveys information an integrating agent needs, with no filler.

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 three-parameter creation tool with no output schema, the description usefully explains what the response contains (the signing secret) and how payloads are signed, which an agent could not infer elsewhere. Minor gaps remain around secret-retention and error behavior, but nothing essential for a correct call is missing.

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 description coverage is 100%, so url, name, and events are already fully documented in the schema, and the description adds no parameter-level meaning such as the wildcard "*" behavior or whether the URL must be unique. Baseline 3 applies when the schema carries the parameter burden.

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?

"Subscribe an endpoint to link events" gives a specific verb (subscribe) and resource (endpoint/link events), so it is clearly a webhook-creation tool rather than the listed list_webhooks, delete_webhook, or test_webhook siblings. It stops short of explicitly contrasting itself with those siblings, which keeps it at 4 rather than 5.

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 description implies when to use it (you want to receive link events at an endpoint) but never states when not to use it or points to test_webhook for verification or list_webhooks for inspection. Usage is inferable from the purpose sentence alone, which is the minimum viable level.

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

Deploy Server