Skip to main content
Glama

update_webhook

Update a webhook endpoint's url, events, description, or status (active or paused). Use it to repoint an endpoint or to pause deliveries without deleting it; unset fields keep their current value. The signing secret does not change. To remove an endpoint use delete_webhook. Requires the webhooks:update scope.

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

Input Schema

NameRequiredDescriptionDefault
urlNoOptional new target URL. Omit to keep the current value.
eventsNoOptional new event type strings. Omit to keep the current value.
statusNoOptional new status, active or paused. Omit to keep the current value.
descriptionNoOptional new description. Omit to keep the current value.
webhook_uuidYesPublic UUID of the webhook endpoint to update.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses partial-update semantics ('unset fields keep their current value'), that the signing secret is immutable, and the webhooks:update scope requirement. It stops short of describing the response payload or side effects on delivery history/queued events, which keeps it from a 5.

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

Conciseness5/5

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

Three tight sentences: what can change first, then the use case and partial-update rule, then the sibling pointer and scope. No filler, nothing buried.

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 5-parameter mutation tool with no annotations and no output schema, the description covers scope, partial-update behavior, secret immutability and the deletion alternative. Only the result of the call (returned object, effect on in-flight deliveries) is unaddressed, which is a minor gap.

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?

Schema description coverage is 100%, so every parameter including the required webhook_uuid is already documented in the schema, and the description mostly restates that omit-to-keep behavior. The one addition — status values 'active or paused' — also appears in the schema, so the description adds little beyond structured data; baseline 3 applies.

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 (update) and resource (webhook endpoint) and enumerates exactly which fields can change (url, events, description, status). An agent can distinguish it from create_webhook, get_webhook and delete_webhook without opening any schema.

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

Usage Guidelines5/5

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

Explicitly frames the two motivating cases (repoint an endpoint, pause deliveries without deleting) and names the alternative for the removal case: 'To remove an endpoint use delete_webhook.' It also states the required scope, so the agent knows authorization prerequisites before calling.

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