Skip to main content
Glama
Sign In
ChatPush MCP Server

ChatPush MCP Server

Official
by ChatPush
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Send bulk message

send_bulk

Send the same message to multiple phone numbers at once for announcements, campaigns, or reminders, with scheduling, UTM tracking, and channel routing.

Instructions

Send the same message to multiple phone numbers at once. Supports scheduling, UTM marks, dispatch routing cascade, Telegram usernames and tdlib user IDs.

Use it for announcements, campaigns or reminders to a list of recipients. For one recipient, or when a delivery ID is needed for tracking, use send_message.

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": {
      "text": "<text>",
      "phones_numbers": "<phones_numbers>"
    },
    "name": "send_bulk"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesMessage text.
utm_markNoLabel for tracking dispatches (see get_utm_tags).
usernamesNoTelegram usernames (tdlib only): requires "tdlib" in dispatch_routing.
sender_nameNoRegistered SMS sender name (see get_balance → sender names).
scheduled_atNoDelayed sending time, format YYYY-MM-DD HH:MM:SS in UTC+0. At least 1 minute and at most 1 month ahead.
tdlib_user_idNoTelegram user ID (positive = private chat, negative = group chat). tdlib channel only.
phones_numbersYesPhone numbers in international format, e.g. ["79991234567", "+995598464533"].
dispatch_routingNoChannels in the order ChatPush should try them (cascade: the next channel is used only if delivery through the previous one fails). whatsapp = WhatsApp, tdlib = personal Telegram account, telegram = Telegram Bot, notify = VK/OK, max = MAX messenger, sms = SMS. If omitted, the account's default routing is used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds useful capability context (scheduling, UTM marks, dispatch cascade, Telegram identifiers) and implicitly warns that no delivery ID comes back from this path. It does not disclose that sends are billable per recipient, whether dispatch is asynchronous, or how the cascade behaves on partial failure — meaningful gaps for a bulk outbound operation.

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 sentences, zero padding. The capability summary comes first and the routing guidance second, so the reader gets scope and the alternative in the order they need them.

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?

With 8 parameters, 2 required, no output schema and a mutation that reaches real recipients, the description covers purpose, usage and the key limitation that tracking IDs come from send_message instead. The remaining gap is outcome behavior — no mention of per-recipient results, cost, or failure handling when part of a list fails across the cascade.

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 coverage is 100%, including the cascade ordering semantics of dispatch_routing and the tdlib-only constraints on usernames and tdlib_user_id, so the baseline of 3 applies. The description's capability list ('scheduling, UTM marks, dispatch routing cascade, Telegram usernames and tdlib user IDs') echoes parameters the schema already documents rather than adding format or constraint detail beyond it.

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

Purpose5/5

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

States a specific verb and resource plus the defining scope constraint: 'Send the same message to multiple phone numbers at once.' That fan-out scope is exactly what separates it from the sibling send_message, so an agent can route between them without opening either schema.

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

Usage Guidelines5/5

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

Gives both sides of the decision: use for 'announcements, campaigns or reminders to a list of recipients,' and explicitly redirects to send_message 'for one recipient, or when a delivery ID is needed for tracking.' The alternative is named with the condition that selects it.

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