Skip to main content
Glama

Create webhook

create_webhook
Destructive

Send events (message.received, message.delivered, message.opted_out, ...) to a URL: your app, a CRM, an automation tool. Returns the signing secret once.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe https URL that receives the events
eventsNoEvent types to receive. Omit, or send "*" or [], for every event. An unknown type is a 400.
numbersNoOptional. Only events about these of your numbers (E.164): message events by their from/to, number events by phone_number. Events about no number (batches, credits, registrations) go only to endpoints without a filter. Omit or [] for every number.
descriptionNoA note on what the endpoint is for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / description / description
      Added value: +"A note on what the endpoint is for"
    • addedInput schema / properties / url / description
      Added value: +"The https URL that receives the events"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Adds real value beyond annotations with 'Returns the signing secret once', which flags a consequential one-time side effect consistent with idempotentHint=false. However, it doesn't explain delivery behavior, retries, or what makes creation 'destructive', and the destructiveHint is left unaddressed.

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 tight sentences: the purpose and event examples lead, and the one-time secret return is front-loaded as the key consequence. Nothing is wasted.

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?

Annotations and a fully described schema carry most of the burden, and the description adds the one-time-secret behavior and event taxonomy. For a create tool with openWorld and destructive hints, it could do slightly more to explain the side effects of starting delivery, but nothing essential to calling it correctly 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 coverage is 100%, so the baseline is 3. The description contributes the concrete event type examples (message.received, message.delivered, message.opted_out) that the schema lacks, but says nothing about url, numbers, or description fields.

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?

Names the specific resource (a webhook endpoint that receives events) and the action of registering one, plus gives concrete event examples. It doesn't explicitly distinguish itself from siblings like update_webhook or test_webhook, but 'Send events ... to a URL' is clear enough to separate create from manage/test.

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?

Implies usage (point event notifications at your app/CRM/automation) but never states when to choose this over update_webhook or test_webhook, nor any prerequisites. Adequate context, no exclusions or alternatives.

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.