Skip to main content
Glama
Sign In
ChatPush MCP Server

ChatPush MCP Server

Official
by ChatPush
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update webhook

update_webhook
Idempotent

Modify an existing webhook's URL or subscribed event types. Send only the fields to change; passing types replaces the entire event list.

Instructions

Update an existing webhook — change its URL or the list of event types it subscribes to. Pass only what should change; types replaces the whole list.

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 ID (from create_webhook or list_webhooks).
urlNoNew URL.
typesNoNew list of event types (replaces the current list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and openWorldHint=true. The description adds the key behavioral detail that the types array wholesale replaces the existing subscription list — a mutation pattern an agent could otherwise get wrong — though it says nothing about permission needs, error behavior, or what happens to in-flight deliveries on URL change.

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?

Two short sentences, front-loaded with purpose, then the partial-update and replacement semantics. No redundant or filler text.

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 three-parameter update tool with a fully documented schema, no output schema, and clear annotations, the description covers the essential decision points: what changes, that fields are optional, and that types is a full replacement rather than a merge. Only failure and permission behavior are left implicit.

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 meaning the schema lacks: omitted fields are left unchanged ('pass only what should change'). It also restates that types replaces the entire list, reinforcing the schema's note, which is the most consequential parameter behavior for this tool.

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 gives a specific verb and resource ('Update an existing webhook') and names the two modifiable aspects, URL and event types. The word 'existing' implicitly differentiates it from create_webhook and delete_webhook, but those siblings are never named explicitly.

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 offers invocation guidance ('Pass only what should change') but no when-to-use guidance relative to alternatives such as create_webhook or delete_webhook. The usage context is only implied by the word 'existing'.

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

Deploy Server

Other Tools