Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Update webhook

update_webhook
Idempotent

Update a webhook's URL or subscribed events within a permitted pod so notifications reach the correct endpoint.

Instructions

Update a webhook's configuration.

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

Input Schema

NameRequiredDescriptionDefault
urlNo
eventsNo
pod_idYesA pod id the key can reach. The server rejects any id outside this key's scope.
webhook_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety and idempotency profile is covered structurally. The description adds nothing on top: it does not say whether fields omitted from the request are left unchanged or cleared, whether the URL is validated, or what permissions the key needs. The pod-scoped rejection rule lives in the schema, not the description.

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

Conciseness3/5

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

The single short sentence is front-loaded and free of padding, so there is no verbosity problem. However, brevity here is under-specification rather than economy — the sentence has room to add partial-update semantics at the same length.

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

Completeness2/5

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

For a four-parameter mutation tool with 25% schema coverage and no output schema, the description should at minimum explain partial-update behavior and the shape of the events field. It provides none of that, leaving the agent to guess at semantics that materially affect the call.

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 description coverage is only 25%; only pod_id is documented in the schema, while url, events, and webhook_id carry no descriptions. The description does not compensate at all — critically, it never states whether an omitted url or events array preserves the existing value or resets it, which is the single most important semantic for an update tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description "Update a webhook's configuration" restates the tool name almost verbatim, adding only the word "configuration". It does not say what aspects of configuration are updatable (url, events) or how it relates to create_webhook, get_webhook, delete_webhook, or test_webhook beyond the obvious verb difference.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no when-not-to-use guidance, and no mention of alternatives such as delete_webhook or create_webhook. The agent must infer entirely from the name that this is the mutation path for an existing webhook.

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