Skip to main content
Glama

create_webhook

Register an HTTPS callback URL to receive HMAC-signed lifecycle events, optionally filtered by event type, so your app can react to job and agent updates.

Instructions

Register a callback URL the platform will POST lifecycle events to (HMAC-SHA256 signed via X-Agents-Signature). Use the verify helper from browsa/webhooks in your receiver.

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
urlYesHTTPS endpoint you control.
eventsNoEvent filter. Omit/empty for ALL events. Examples: job.completed, job.failed, agent.started.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose valuable behavior beyond the schema: delivery is outbound POSTs, payloads are HMAC-SHA256 signed, and the signature header is X-Agents-Signature. It omits permission requirements, retry/failure behavior, duplicate-URL handling, and whether a signing secret is returned.

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 with the core purpose front-loaded and the signing detail immediately after. Nothing is redundant or padded.

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

Completeness3/5

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

For a simple two-parameter creation tool with no output schema and no annotations, the description covers purpose and payload security well. It leaves a gap around what the call returns (webhook ID, signing secret) and any preconditions, which matters more here because nothing else supplies that context.

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 baseline is 3. The description reinforces the 'events' parameter by framing them as lifecycle events but adds no format or semantics beyond what the schema already documents with examples.

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 gives a precise verb+resource ('Register a callback URL') plus the exact mechanism ('the platform will POST lifecycle events to'). 'Register' cleanly separates it from delete_webhook and list_webhooks without needing to name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to choose this tool versus siblings like create_schedule or create_schedule-style automation. The only guidance offered ('Use the verify helper from browsa/webhooks in your receiver') concerns the receiver implementation, not tool selection.

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