Skip to main content
Glama

create_webhook

Create a new webhook. Available events: post.scheduled, post.published, post.failed, post.approved (the last approval of a post's approval workflow is in), post.rejected (an approver rejected the post)

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
urlYesThe HTTPS URL to send events to
eventsYesEvents to subscribe to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already declare it is a non-destructive mutation that touches an open-world target, so the description would need to add auth, rate-limit, or return-value context. Instead it says nothing about whether a signing secret is issued (rotate_webhook_secret exists as a sibling, hinting one is), whether delivery is retried, or what is returned on success. For a mutating tool with no output schema, this leaves the agent guessing.

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 sentences, front-loaded with the action, then the event vocabulary. Nothing is wasted, and the parenthetical clarifications earn their space by disambiguating approval semantics.

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?

Valid event names are covered well, but with no output schema the description should say what a successful call yields — the webhook id and, if applicable, a signing secret the caller must store. That gap matters for a create-and-configure tool.

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?

Schema coverage is 100% for both parameters, so the baseline would be 3, but the description adds the concrete list of accepted event names for the `events` array, which the schema leaves as unconstrained strings with no enum. It even clarifies the trickier post.approved and post.rejected semantics.

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 new webhook'. It is unambiguous and clearly distinct from delete_webhook and update_webhook, though it does not explicitly contrast with them.

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?

Usage is implied by the verb — subscribe to events — but the description never states preconditions, when to prefer create_webhook over an existing webhook, or limits such as the maximum number of webhooks. No alternatives are named or excluded.

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.

Resources