Skip to main content
Glama

webhooks-create

Create a webhook

Create a webhook subscribed to one or more event types. Deliveries use the v2 envelope and are signed with the project signing secret (see the signing secret endpoint).

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": {
      "request": "<request>"
    },
    "name": "webhooks-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: deliveries use the v2 envelope and are signed with the project signing secret, with a pointer to the signing secret endpoint. It still omits whether the URL must be reachable/verified at creation time and what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is two short sentences, front-loaded with the action and followed by the delivery/signature detail. The opening line 'Create a webhook' duplicates the annotation title and is slightly redundant, but no sentence is wasted.

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 one-parameter, nested-object mutation with no output schema, the description covers what the tool does and how deliveries behave, but leaves gaps an agent would care about: whether the created webhook's ID or secret is returned, whether a verification handshake is required, and any failure modes. Adequate but not complete.

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?

Reported schema description coverage is 0% at the top level (the single 'request' parameter is undocumented), so the description should compensate more than it does — it only echoes that eventTypes accepts one or more values. The nested field descriptions for url, name, eventTypes, description, and projectId are rich, which keeps this at a minimum-viable 3 rather than lower.

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?

The description states a specific verb and resource ('Create a webhook') and clarifies that the subscription can cover one or more event types, which distinguishes it from webhooks-update, webhooks-list, and webhooks-retrieve. It doesn't explicitly name a sibling, but the create semantics are unambiguous against the webhooks-* family.

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 only implied by the verb: an agent can infer 'use this to register a new webhook rather than modify an existing one,' but there is no explicit when-to-use or when-not (e.g., use webhooks-update for changes, delete before re-creating). Prerequisites such as key scoping live in the nested projectId schema text, not the description.

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