Skip to main content
Glama

Add webhook

add_webhook

Add a webhook URL that receives delivery events. Paid plans only.

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": "add_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYeshttps URL
eventsNoEvent names, see list_webhooks
all_eventsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the write-and-external-facing nature is covered. The description adds the plan-gating constraint, which is useful context beyond the annotations. It does not disclose whether a secret/signing key is created, whether URL reachability is validated at creation time, or what happens on failure, leaving noticeable gaps for a mutation with external side effects.

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?

Two short sentences with no filler, and the core action is front-loaded. The plan restriction is the only additional sentence and it earns its place, though the overall brevity leaves the definition thin rather than tight.

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?

There is no output schema, so the description could reasonably mention what is returned (webhook id, secret, active state). For a three-parameter creation tool with an open-world flag, the definition covers purpose and the plan gate but leaves the events/all_events relationship and post-creation state unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%: url ('https URL') and events ('Event names, see list_webhooks') are described, but all_events has no description anywhere. The description adds no parameter meaning at all, and crucially does not clarify the likely interaction between events and all_events (e.g., mutual exclusivity or override behavior), which is exactly the kind of ambiguity prose should resolve.

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: 'Add a webhook URL that receives delivery events.' This is clearly a creation operation, implicitly distinct from the sibling delete_webhook, test_webhook, and set_webhook_enabled, though no sibling is named explicitly.

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?

'Paid plans only' is a genuine prerequisite that tells an agent when this call will fail, which is more than nothing. However, there is no guidance on when to prefer this over alternatives (e.g., test_webhook to validate before/after adding), no mention of webhook-count limits, and no statement about prerequisites such as domain verification.

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