Skip to content
All tools

telegram_send_message

Telegram · macOS · Windows

Effect: send (strongest supported action). Status: gated.

Gated means the tool requires an installed app, a connected account, permission, or runtime availability. Check those requirements on the listed platform before using it.

macOS

Purpose

Sends a Telegram message from your own account to one chat. WRITE operation with a preview: the first call (confirm=false) returns a preview and sends NOTHING; show it to the user and call again with confirm=true only after they approve. chat_id MUST come from telegram_list_chats — never invent one. One message per call; no bulk sending.

Required inputs

Permissions and confirmation

Explicit confirmation parameter: inspect the schema and tool description before any real call. The documentation example keeps confirm false. Obtain user authorization before performing the action.

Full input schema — macOS
{
  "properties": {
    "account": {
      "description": "Which linked Telegram account to use: its label or id from telegram_list_accounts. Leave it out to use the default account.",
      "type": "string"
    },
    "chat_id": {
      "description": "Chat id from telegram_list_chats.",
      "type": "string"
    },
    "chat_name": {
      "description": "The chat's name as telegram_list_chats showed it, echoed in the preview so the user sees who receives it.",
      "type": "string"
    },
    "confirm": {
      "description": "Must be true to actually send. Without it, returns a preview.",
      "type": "boolean"
    },
    "message": {
      "description": "Text to send (max 4096 characters).",
      "type": "string"
    }
  },
  "required": [
    "chat_id",
    "message"
  ],
  "type": "object"
}

Documentation example

Do not execute this example. These concrete inputs refer to a fictional demonstration dataset. Resolve real handles and obtain user authorization before any real call.

{
  "chat_id": "5550100123",
  "confirm": false,
  "message": "Can we review the launch checklist on Tuesday?"
}

Windows

Purpose

Sends a Telegram message from your own account to one chat. WRITE operation with a preview: the first call (confirm=false) returns a preview and sends NOTHING; show it to the user and call again with confirm=true only after they approve. chat_id MUST come from telegram_list_chats — never invent one. One message per call; no bulk sending.

Required inputs

Permissions and confirmation

Explicit confirmation parameter: inspect the schema and tool description before any real call. The documentation example keeps confirm false. Obtain user authorization before performing the action.

Full input schema — Windows
{
  "properties": {
    "account": {
      "description": "Which linked Telegram account to use: its label or id from telegram_list_accounts. Leave it out to use the default account.",
      "type": "string"
    },
    "chat_id": {
      "description": "Chat id from telegram_list_chats.",
      "type": "string"
    },
    "chat_name": {
      "description": "The chat's name as telegram_list_chats showed it, echoed in the preview so the user sees who receives it.",
      "type": "string"
    },
    "confirm": {
      "description": "Must be true to actually send. Without it, returns a preview.",
      "type": "boolean"
    },
    "message": {
      "description": "Text to send (max 4096 characters).",
      "type": "string"
    }
  },
  "required": [
    "chat_id",
    "message"
  ],
  "type": "object"
}

Documentation example

Do not execute this example. These concrete inputs refer to a fictional demonstration dataset. Resolve real handles and obtain user authorization before any real call.

{
  "chat_id": "5550100123",
  "confirm": false,
  "message": "Can we review the launch checklist on Tuesday?"
}