Skip to main content
Glama

webhooks-update

Destructive

Update a webhook

Update a webhook. Legacy v1 webhooks are read-only: delete them and create a new webhook instead.

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": {
      "request": "<request>"
    },
    "name": "webhooks-update"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is largely covered. The description adds the useful legacy-v1 read-only rule, but says nothing about whether the update is a partial patch or a full replacement (i.e., whether omitted fields such as url or eventTypes are cleared), which matters a lot for a destructive operation.

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?

It is short and front-loaded, but the opening line merely restates the title and the second sentence repeats "Update a webhook" a third time. The one genuinely informative clause, the legacy v1 rule, is buried after the redundancy.

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

Completeness3/5

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

For a destructive mutation with a nested body object and no output schema, the description covers the notable legacy constraint but omits partial-vs-full update semantics and scope/permission notes. Adequate to avoid the biggest trap, not enough to call the tool confidently.

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 registers as 0%, but the schema itself inline-documents id, url, name, eventTypes, description, and projectId. The description adds no parameter meaning of its own beyond the legacy constraint, so it neither compensates for the coverage metric nor introduces confusion.

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?

The description uses a specific verb and resource ("Update a webhook") and adds a meaningful constraint about legacy v1 webhooks being read-only. It does not explicitly name sibling tools like webhooks-create or webhooks-delete, but the delete-and-recreate workaround implicitly points at them, so an agent can distinguish this from the create path.

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?

It states an explicit when-not case (legacy v1 webhooks cannot be updated) and names the alternative workflow (delete, then create a new webhook). What is missing is guidance on when to prefer this tool over delete+create for v2 webhooks, or any prerequisite/auth context.

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