Skip to main content
Glama

Create Event Webhook

create_event_webhook

Subscribe a public HTTPS endpoint to registration.created, sale.completed and/or refund.completed for an event you host. Signing secret is returned ONCE. Use a unique request_id; retries with the same ID do not create another endpoint or reveal the secret again. Deliveries contain resource IDs and amounts; read guest/sale APIs for contacts and answers. Requires a write key. Max five active endpoints per event.

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

Input Schema

NameRequiredDescriptionDefault
urlYes
eventsYes
event_idYes
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the highest-value behavioral facts: the signing secret is revealed exactly once, request_id deduplicates retries so no duplicate endpoint is created, deliveries carry only resource IDs and amounts, and there is a hard cap of five active endpoints. These are exactly the consequences an agent cannot infer from readOnlyHint/destructiveHint/openWorldHint. The idempotentHint=false annotation is best read as 'not inherently idempotent without the dedupe key', which the description's request_id sentence actually clarifies rather than contradicts.

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?

Five short sentences, front-loaded with the core action and scope, then the one-time secret warning, then dedupe mechanics, then payload/limit caveats. Nothing is repeated from the schema and no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no output schema and zero schema description coverage, the definition covers what matters: required credential, the one-time secret return, retry semantics, payload contents, and a quota. An agent has enough to call it correctly and to warn the caller about the irreversible secret exposure.

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?

With 0% schema description coverage, the description does most of the semantic work: it explains that url must be a public HTTPS endpoint, enumerates the three subscribable event types, ties event_id to an event you host, and defines request_id as a unique dedupe key. It omits formatting constraints the schema carries (event_id pattern, request_id minimum length), but the meaning an agent needs to construct a valid call is largely present.

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 first sentence names a specific verb (subscribe), the exact resource (a public HTTPS endpoint), and the precise event types covered (registration.created, sale.completed, refund.completed) scoped to 'an event you host'. This is unambiguous and lets an agent distinguish it from siblings like list_event_webhooks or revoke_event_webhook without opening a 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?

The description gives clear operating context: a write key is required, only five active endpoints are allowed per event, and retries must reuse the same request_id. It even steers the agent away from expecting contact data by pointing to the guest/sale APIs. It stops short of explicitly naming the sibling tools for listing or revoking endpoints, so there is no direct 'use X instead when...' routing.

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.