Skip to main content
Glama

Update webhook

update_webhook
Destructive

Change a webhook endpoint: URL, events, or turn it off (active: false).

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
idYesWebhook endpoint id
urlNoThe https URL that receives the events
activeNofalse pauses delivery; pending retries for a paused endpoint are dropped.
eventsNoEvent types to send, or * for all
numbersNoReplace the number filter; [] or null clears it.
descriptionNoA note on what the endpoint is for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / description / description
      Added value: +"A note on what the endpoint is for"
    • addedInput schema / properties / events / description
      Added value: +"Event types to send, or * for all"
    • addedInput schema / properties / url / description
      Added value: +"The https URL that receives the events"
  2. 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, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds a small operational hint ('turn it off (active: false)') but does not elaborate on destructive effects, retry dropping, or non-idempotent behavior beyond what annotations and schema already indicate.

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?

A single, front-loaded sentence with no filler. It communicates the core action and key fields efficiently.

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?

The tool is a mutation with six parameters, rich annotations, and a fully documented schema. The description is adequate for the core update action but omits routing guidance against alternatives and does not mention the effects of pausing via active: false, leaving some contextual gaps.

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 the schema already documents all six parameters. The description only restates URL, events, and active, and adds no semantics beyond the schema, which is the baseline expectation when schema coverage is complete.

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 states a specific verb ('Change') and resource ('webhook endpoint'), and names the main editable fields (URL, events, active). It is clear what the tool does, though it does not explicitly distinguish itself from siblings like create_webhook or delete_webhook.

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?

Usage is implied by 'Change a webhook endpoint' and the mention of turning it off via active: false. However, there is no explicit guidance on when to use this versus create_webhook, delete_webhook, or rotate_webhook_secret.

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.