Skip to main content
Glama
1msg MCP

1msg MCP

Official
by 1msg

get_webhook

Retrieve configured webhook URLs for a channel and their delivery status to see which endpoints receive events and which are skipped.

Instructions

Return the webhook URL(s) currently configured for this channel, plus delivery status for each URL.

webhookUrl is a string when a single URL is set, an array of strings when multiple URLs are configured, or null if none is set.

Prefer webhookStatuses. The circuit breaker is per URL, not per channel. If 1 of 4 URLs is sticky-disabled, that URL is skipped; the other three still receive events. Send/receive are not affected.

Channel-level haveDisabledWebhooks, circuitState, reason, fails, trips, and timestamps are a compatibility summary of one URL (the first sticky-disabled URL, else the first configured URL). They are not "the channel is dead".

  • haveDisabledWebhooks — true when at least one URL in webhookUrl is sticky auto-disabled. Live URLs still get events.

  • circuitState — compressed scalar for that same primary URL: ok | degraded | open | half_open | disabled.

  • disabledWebhooks — currently configured URLs that are sticky-disabled (subset of webhookUrl).

  • webhookStatuses — one row per currently configured URL. Use this array to see which endpoints are live vs skipped.

  • fails / trips / firstFailAt — diagnostics for support, not product UI. fails = failures in a rolling ~10 minute window (not lifetime). trips = failed recovery probes on the 15 min → 1 h → 6 h schedule (sticky disable after 3). Clients can ignore these and use webhookStatuses + disabledWebhooks only.

Sticky disable skips delivery; it does not unconfigure the URL (it stays in webhookUrl). Re-enable with POST /webhook or POST /settings. Those endpoints replace the whole list — with multiple URLs, send the full array.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so well: it discloses the per-URL rather than per-channel circuit breaker, that sticky disable skips delivery but keeps the URL configured, that live URLs still receive events, and that fails/trips are support diagnostics on a rolling ~10 minute window. It also states that re-enabling requires POST /webhook or POST /settings, which replaces the entire list — a mutation hazard an agent could not learn from the schema.

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?

It is long but front-loaded and well structured with bullets and inline code for field names. There is some duplication — haveDisabledWebhooks is explained twice ('at least one URL is sticky-disabled' reappears in the bullet) and the 'not the channel is dead' framing is repeated — but nearly every line carries operational meaning.

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?

There is no output schema, so the description must document return shape and field meaning, and it does so thoroughly, including the compatibility-summary fields, the primary-URL selection rule, and how to recover from sticky disable. An agent has everything it needs to call the tool and interpret the result correctly.

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?

The tool takes zero parameters, so the baseline is 4. The description instead spends its words on return-value semantics (webhookUrl string vs array vs null, the five circuitState values), which is appropriate for a no-arg getter.

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?

Opens with a specific verb and resource: 'Return the webhook URL(s) currently configured for this channel, plus delivery status for each URL.' That clearly separates it from set_webhook (referenced as `POST /webhook` for re-enabling), though it does not name the sibling tools directly.

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?

The description gives strong guidance on how to interpret the result ('Prefer `webhookStatuses`', clients can ignore fails/trips), but that is read guidance, not selection guidance. It never states when to call get_webhook instead of list_settings, get_status, or get_calling_settings, so an agent must infer that this is the webhook-diagnostics tool.

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