Skip to main content
Glama

list_webhooks

Read-only

List all configured webhooks with their status, events, and last trigger time: the webhooks of the active workspace and the organisation-wide webhooks made in the OmniSocials dashboard (scope 'Organisation': they receive the events of every workspace). A webhook switches off by itself when the person who set it up no longer has access to the organisation or workspace (status Inactive, the reason under Last failure in get_webhook); update_webhook with is_active true switches it on again.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare read-only/open-world=false; the description adds genuinely non-obvious behavior — webhooks auto-disable when their creator loses organisation or workspace access, surface as status Inactive, and can be restored via update_webhook. That is exactly the kind of lifecycle context an agent cannot infer from structured fields.

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?

Front-loaded with purpose and returned fields, then scope, then lifecycle behavior — a logical order. The second sentence is long and dense, stacking the auto-disable condition, the status name, the pointer to get_webhook, and the fix in one breath, but no sentence is filler.

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?

With no output schema, the description carries the return-shape burden and does so by naming status, events, and last trigger time. Combined with the scope definition and the auto-disable explanation, an agent has everything needed to call and interpret this 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?

The tool takes zero parameters, so the baseline is 4. The description does not mention that no filtering (by status, event, or workspace) is available, which would have been a small clarifying addition, but there is nothing else to document.

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?

States a specific verb and resource ('List all configured webhooks') and names the returned fields (status, events, last trigger time). It also distinguishes scope precisely: the active workspace's webhooks plus organisation-wide ones, with a parenthetical explaining what 'Organisation' scope means.

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

Usage Guidelines4/5

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

Implicitly routes the agent: it points to get_webhook for the failure reason behind an Inactive status and to update_webhook with is_active true to re-enable one. It does not explicitly say when to prefer this over get_webhook for a single webhook, but the enumeration-vs-detail split is clear enough.

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