Skip to main content
Glama

update_webhook

Destructive

Update a webhook's URL, events, or active status. Works on workspace and organisation-wide webhooks. Switching a webhook on (also after it switched off by itself) makes the connected user the person behind it. Setting a URL on an organisation-wide webhook (even its current one) moves it to the active workspace: from then on it receives only that workspace's events (get_webhook shows the new scope; an organisation-wide webhook is made in the OmniSocials dashboard).

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": {
      "id": "<id>"
    },
    "name": "update_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe webhook ID to update
urlNoUpdated HTTPS URL
eventsNoUpdated event list
is_activeNoEnable or disable

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the destructiveHint/openWorldHint annotations by disclosing non-obvious side effects: re-enabling a webhook transfers ownership to the acting user, and setting a URL on an org-wide webhook narrows it to the current workspace even if the URL is unchanged. It also tells the agent how to verify the resulting state via get_webhook.

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 core action and its targets are front-loaded in the first sentence, with side effects following. The final sentence is dense and parenthetical, but every clause carries distinct information about scope or ownership.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with no output schema, the description covers the important irreversible-feeling consequences and points to get_webhook for verification. It leaves out whether updates are partial or full-replacement when optional fields are omitted, which is the main remaining ambiguity.

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%, so the baseline is 3, but the description adds real semantics the schema lacks: is_active toggling reassigns ownership, and url assignment has a scope side effect independent of the value written. It does not clarify partial-update behaviour for omitted fields.

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 plus the exact mutable fields (URL, events, active status), which maps one-to-one onto the schema properties and clearly separates it from get_webhook, create_webhook and delete_webhook. An agent can tell what this does without opening the schema.

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?

It establishes the applicable scope ('works on workspace and organisation-wide webhooks') and notes that org-wide webhooks are created in the OmniSocials dashboard, which implicitly rules out creating them here. However, no sibling is named as an alternative and there are no explicit when-not conditions, so guidance is conditional rather than directive.

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