Skip to main content
Glama

domani

by run.domani

Create Webhook

create_webhook

Register a new webhook endpoint to receive event notifications. The URL must use HTTPS. Optional Authorization or X-API-Key headers are encrypted and sent with every delivery. The webhook secret is returned only once - save it to verify incoming payloads with HMAC-SHA256.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesHTTPS URL that will receive webhook POST requests
eventsYesEvent types to subscribe to, e.g. ["domain.purchased", "dns.updated"]. Use list_webhook_events to see all available types.
headersNoOptional auth headers. Only Authorization and X-API-Key are accepted; values are encrypted and never returned.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / headers
      Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "description": "Optional auth headers. Only Authorization and X-API-Key are accepted; values are encrypted and never returned.",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations present, the description carries the transparency burden. It usefully discloses that Authorization/X-API-Key headers are encrypted and sent with every delivery, that the webhook secret is returned only once, and that HMAC-SHA256 should be used for verification. It does not describe the write-side behavior of creating a resource explicitly, but 'Register a new endpoint' implies mutation.

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 focused sentences deliver a clear purpose, HTTPS requirement, security context, and secret-handling note without repeating the schema or adding filler. The most important onboarding information is front-loaded in the first sentence.

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?

The description covers the key operational details for calling the tool: HTTPS requirement, restricted headers, encryption behavior, event subscription purpose, and one-time secret handling. Since there is no output schema, the note that the secret is returned only once is valuable, but a bit more detail about response shape or webhook ID would make it fully complete.

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 the schema already explains url, events, and headers. The description adds context about HTTPS enforcement and header encryption/secret handling, but it does not substantially expand the meaning of the parameters beyond what the schema already provides.

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?

The description states a specific action ('Register a new webhook endpoint') on a clear resource, with the purpose of receiving event notifications. The word 'new' and the registration framing distinguish it from delete_webhook, update_webhook, and list_webhooks 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 description implies when to use the tool: when the agent needs to register an endpoint for event notifications, and it gives a precondition (HTTPS URL). However, it does not explicitly mention alternative webhook tools like update_webhook, list_webhooks, or delete_webhook, or state when those should be used instead.

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

All domani toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation3/5

While most tools have distinct purposes, several clusters overlap significantly (e.g., check_email, check_email_deliverability, get_email_deliverability, get_domain_email_status; buy_domain, buy_aftermarket, acquire_domain). The descriptions are detailed and help differentiate, but the sheer number of tools makes it challenging for an agent to select the correct one without careful reading.

Naming Consistency3/5

The dominant pattern is verb_noun with underscores (e.g., create_mailbox, list_domains), but there are notable inconsistencies: destructive actions mix delete/remove/cancel/revoke/unsell, and a few names deviate entirely (search, dns_check, domain_status). The pattern is recognizable but not uniformly applied.

Tool Count1/5

With 122 tools, this vastly exceeds the 50+ threshold for extreme mismatch. Even for a comprehensive domain and email platform, the tool count is overwhelming and will likely hinder agent performance through excessive choice and context bloat.

Completeness4/5

The server covers a wide range of domains, DNS, email, marketplace, negotiations, transfers, webhooks, tokens, and billing. Minor gaps exist, such as no update operation for mail rules, no direct domain deletion, and limited mailbox configuration beyond forwarding and credentials, but most lifecycle workflows are supported.

Resources