ChatPush MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Create webhook

create_webhook

Register an HTTPS webhook URL to receive real-time POST notifications for selected ChatPush events, enabling servers, CRMs, or automation tools to react to incoming messages and delivery status updates.

Instructions

Register a webhook URL to receive real-time notifications for specific ChatPush events (e.g. whatsapp_log_out, delivery status updates, incoming messages). Use it when the user wants their server, CRM or automation (n8n, Make, Zapier) to receive replies or react to WhatsApp/Telegram events.

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": {
      "url": "<url>",
      "types": "<types>"
    },
    "name": "create_webhook"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	HTTPS URL to receive notifications as POST requests.
`types`	Yes	Event types: whatsapp_log_out (WhatsApp account disconnected); whatsapp_log_in (WhatsApp account connected); whatsapp_incoming_msg (incoming and outgoing WhatsApp messages (with file download links) and incoming WhatsApp calls); tdlib_incoming_msg (incoming and outgoing personal Telegram messages (with file download links) and Telegram calls); max_incoming_msg (incoming and outgoing messages of a connected MAX account); whatsapp_status_msg (statuses of outgoing WhatsApp messages: sent, received, read, played, failed, expired, …).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 4, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true and destructiveHint=false, so the mutation and outbound-network profile is covered. The description adds that notifications are real-time, but the POST-delivery detail is already in the url schema field, and it says nothing about whether re-registering the same URL creates duplicates, any authentication/verification handshake, or rate limits.

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

Conciseness4/5

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

Two sentences, front-loaded with the action and followed by the intent, with no filler or repetition. The parenthetical list of automation platforms is slightly expendable but plausibly aids intent matching, so it largely earns its place.

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 two-parameter, fully documented schema with annotations and no output schema, the description covers what the tool does and when to call it. The remaining gap is minor: it does not indicate what comes back on success (e.g. a webhook identifier) or how to verify the registration afterwards.

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%, and the types field already enumerates and explains every event type in detail. The description only echoes a few event examples (whatsapp_log_out, delivery status updates, incoming messages), adding no syntax, format, or selection guidance beyond the schema, so the baseline 3 applies.

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: 'Register a webhook URL' to receive notifications for named ChatPush events, with concrete examples (whatsapp_log_out, delivery status, incoming messages). It is clearly distinct from get_webhook/list_webhooks/delete_webhook by implication, but it never names those siblings or states that registration creates a new webhook rather than modifying one, so it stops short of full differentiation.

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?

'Use it when the user wants their server, CRM or automation (n8n, Make, Zapier) to receive replies or react to WhatsApp/Telegram events' gives a concrete triggering intent that an agent can match against user requests. It offers no exclusions, though — nothing says to use update_webhook for an existing endpoint or list_webhooks to inspect current registrations.

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