Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Create webhook

create_webhook
Destructive

Creates a webhook endpoint subscribed to one or more events, requiring a public HTTPS URL, and returns the endpoint with its one-time signing secret.

Instructions

Create a webhook endpoint subscribed to one or more events. The URL must be a public https endpoint. Returns the endpoint AND its signing secret (shown only 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>",
      "events": "<events>"
    },
    "name": "create_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic https endpoint URL
eventsYesEvent names (use list_webhook_event_types for the authoritative list)
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / required
      Added value: +[
      +  "url",
      +  "events"
      +]
  2. First observedv0.73.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so safety framing is covered; the description adds genuinely non-obvious behavior by disclosing that the response includes the endpoint plus a signing secret shown only once. That one-time secret is a consequence an agent must know before calling, since losing it requires rotate_webhook_secret. It leaves out idempotency/duplicate-endpoint behavior and any permission requirements.

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 core action, then the constraint, then the return behavior. Every sentence carries distinct information and nothing is padded.

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?

With no output schema, the description usefully states what comes back (endpoint and one-time signing secret), which is the key return-value fact. For a three-parameter creation tool with destructive/openWorld annotations already set, remaining gaps, such as auth needs and duplicate handling, are modest rather than disqualifying.

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 67% and the description largely restates what the schema already says: 'public https endpoint' duplicates the url field description verbatim in substance, and the event-type pointer duplicates the events field description. The third parameter, description, is undocumented in both places, and the description does not compensate for that gap. Baseline 3 fits.

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?

States a specific verb and resource ('Create a webhook endpoint') plus the scoping detail that it is subscribed to one or more events. An agent can separate it from delete_webhook, update_webhook, or rotate_webhook_secret purely on the name plus this sentence, though the description itself never names a contrasting sibling.

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?

It gives two prerequisites: the URL must be a public https endpoint and event names should come from list_webhook_event_types. That is real usage context, but there are no exclusions (when not to create), no mention of checking for an existing endpoint versus calling update_webhook, and no auth or permission preconditions.

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

Deploy Server

Other Tools