Skip to main content
Glama

messages_send

Destructive

Send a message to a thread, channel, or contact. Supports Telegram, Email, LinkedIn, and other connected channels. For LinkedIn posts (comment_thread kind), this posts a comment on the post. Can automatically resolve recipients and channels when not specified. In a Telegram bot supergroup with Topics, a reply stays in its topic and topic_id posts into one without replying. Can send files/images/documents as attachments — pass attachments=[file_id, ...] with integer file IDs obtained from collections.list_files, search.files, or files.search. text is optional when attachments are provided.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "messages_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoMessage text to send. Optional if attachments provided.
formatNoMessage formattext
silentNoSend without notification
buttonsNoInline reply buttons shown under the message, one per row (max 10). Each item is {"label": "<visible button text>"} plus exactly one target: "value" (a string sent back as a normal incoming message when tapped, defaults to the label, max 64 bytes), "url" (opens a link) or "web_app" (opens an https page as a Telegram Mini App). A "url" button may add "track": true: the tap is then counted for this conversation (analytics_link_clicks_v in analytics.query) and the person is sent on to the url; "tag": <ai_tag id> beside it also puts that tag on the CONVERSATION at the tap (a group's tag is any member's tap; a first message to a new contact has no conversation yet and goes out untagged); "pass": "<name>" opens the url with <name>=<the chat's id on its channel> added, so the site can name the person back in its own events; "pass_source": "<name>" adds <name>=<where the chat came from> (a bot link's start parameter, an ad's ref; nothing when unknown); a "web_app" button takes "pass" and "pass_source" too (no track): they are written into its url when the message is sent. Only on channels that support buttons (Telegram bot accounts); can accompany at most one attachment, and when the text is too long for a media caption the buttons arrive with the text as a second message.
mentionsNoPeople of a group chat to @-tag so the platform really notifies them (WhatsApp, Telegram groups). Each item names one member of THIS chat by one of: "name" (as shown in the chat), "phone" (international number) or "entity_id". If the text already holds "@<name>" that spot is the tag, otherwise "@<name> " is put in front of the text. A person passed here who is not in the chat, or who matches several, refuses the whole send and lists the members. Without this parameter a "@Name" in the text of a group message tags the member it names in the same way; an @-word that names nobody, or several members, refuses the send on WhatsApp, while on Telegram the message goes out with that word as plain text and the result's "warnings" names it (it tagged nobody: check them and pass mentions). Not combinable with attachments or buttons, and not available while the agent sends drafts. Text may be empty: the tags alone are sent.
templateNoWhatsApp Business API only. An approved template to send instead of free text, in Meta's shape: {name, language, components:[{type:'body', parameters:[{type:'text', text:...}]}, ...]}; `language` is the code as a string ('en_US'). Required when the 24-hour window of the conversation is closed (the send answers WINDOW_EXPIRED otherwise). Read the approved templates and their variables with channels.list(account_id=...).
topic_idNoForum topic to post into, without replying (Telegram bot supergroups with Topics; the topic_id that messages.read_history shows on a message). A reply to a message of a topic stays in that topic by itself; this overrides it. Refused on channels without topics.
trace_idNoOnly when this message is your reply to an agent task DialogBrain handed to you: that task's Trace ID. The message is then filed as the agent's reply, not as a person taking the conversation over (which would pause the agent there). OMIT when a person is writing.
thread_idNoTarget thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. To write to a phone number nobody has a thread with yet: 'whatsapp:+<number in international format>' writes to it from a personal WhatsApp account (from_account_id picks which one), 'viber:+<number in international format>' writes to it from the workspace's own Viber number (from_account_id picks which one), 'whatsapp_business:+<number in international format>' opens a WhatsApp conversation from a WhatsApp Business API number (from_account_id picks which one; the first message must be a `template`), and 'sms:+<number>' texts it from a workspace phone number that has SMS turned on (from_account_id picks which one), landing in that number's conversation with the recipient, next to their calls. 'x:@<handle>' sends a first X direct message to that person from a connected X account; X refuses it when their inbox is closed to the sender. 'discord:<user id>' (the person's numeric Discord id) sends a first Discord DM from a connected Discord account, into the DM that exists with them or one opened for it; new DMs are limited per account and day, and refused in words with a retry_after when over. 'skool:user:<user id>' (optionally '@<community id>' after the id, when the two share several communities) sends a first message on Skool from a connected Skool account; a Skool post thread ('skool:<account>:post:<post id>') takes a comment instead. NEVER use a chat-type word (dm, group, channel, livechat, comment_thread) — those are category labels from the SITUATION block, not ids.
as_documentNoSend image attachments as files (documents) instead of photos, so the channel does not recompress them (Telegram: full-quality PNG/JPEG with the original filename). A single image already goes as a file; several go as one album of files, after any photo attachments, with the caption on the first album. Ignored on channels that have no such distinction.
attachmentsNoArray of integer file IDs to send as attachments (images, documents, any files). Get file IDs from collections.list_files (field `file_id`), search.files (field `file_id`), or files.search — only ids returned by those calls in this workspace. The file must already exist in the workspace (status=ready) — no separate upload step needed. When attachments are provided, `text` becomes optional (a caption can be included alongside).
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
private_replyNoComment threads only (Instagram, Facebook): answer the comment in the commenter's private messages instead of publicly under the post (Meta's Private Replies). One message per comment, within 7 days of the comment. The message is filed in the person's private conversation. To also answer publicly, make a second call without this flag. OMIT for a normal send.
recipient_nameNoName of a person already in contacts (e.g., 'Jane', 'John'). Tool will auto-resolve channel. Optional if thread_id provided. Not for a phone number: a new number goes in thread_id (see there).
from_account_idNoWhich of the workspace's accounts on this channel SENDS the message, i.e. the number or handle the recipient sees. A numeric thread_id is one conversation on one account: naming a different account for it is refused. With a channel_ref or recipient_username, the conversation ON THIS ACCOUNT is used, or opened where the channel can start one; if it has none, the send is refused rather than made from another account. OMIT and the platform picks the most recently active account, which is a coin flip in a workspace with several numbers: pass it whenever one of them must not be used to open conversations (a personal line, or one under a spam restriction). An account that is not active in this workspace is refused, never silently swapped.
recipient_usernameNoTelegram @username to message (e.g. '@some_username'). Use this for a Telegram user NOT yet in contacts — it resolves the handle, adds the contact, and creates the thread. Telegram only; for existing contacts prefer thread_id or recipient_name.
reply_to_message_idNoID of message to reply to (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / topic_id
      Added value: +{
      +  "description": "Forum topic to post into, without replying (Telegram bot supergroups with Topics; the topic_id that messages.read_history shows on a message). A reply to a message of a topic stays in that topic by itself; this overrides it. Refused on channels without topics.",
      +  "type": "integer"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / trace_id
      Added value: +{
      +  "description": "Only when this message is your reply to an agent task DialogBrain handed to you: that task's Trace ID. The message is then filed as the agent's reply, not as a person taking the conversation over (which would pause the agent there). OMIT when a person is writing.",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / buttons / description
      Previous value: -"Inline reply buttons shown under the message, one per row (max 10). Each item is {\"label\": \"<visible button text>\"} plus exactly one target: \"value\" (a string sent back as a normal incoming message when tapped, defaults to the label, max 64 bytes), \"url\" (opens a link) or \"web_app\" (opens an https page as a Telegram Mini App). A \"url\" button may add \"track\": true: the tap is then counted for this conversation (analytics_link_clicks_v in analytics.query) and the person is sent on to the url; \"tag\": <ai_tag id> beside it also puts that tag on the CONVERSATION at the tap (a group's tag is any member's tap; a first message to a new contact has no conversation yet and goes out untagged); \"pass\": \"<name>\" opens the url with <name>=<the chat's id on its channel> added, so the site can name the person back in its own events; \"pass_source\": \"<name>\" adds <name>=<where the chat came from> (a bot link's start parameter, an ad's ref; nothing when unknown). Only on channels that support buttons (Telegram bot accounts); can accompany at most one attachment, and when the text is too long for a media caption the buttons arrive with the text as a second message."New value: +"Inline reply buttons shown under the message, one per row (max 10). Each item is {\"label\": \"<visible button text>\"} plus exactly one target: \"value\" (a string sent back as a normal incoming message when tapped, defaults to the label, max 64 bytes), \"url\" (opens a link) or \"web_app\" (opens an https page as a Telegram Mini App). A \"url\" button may add \"track\": true: the tap is then counted for this conversation (analytics_link_clicks_v in analytics.query) and the person is sent on to the url; \"tag\": <ai_tag id> beside it also puts that tag on the CONVERSATION at the tap (a group's tag is any member's tap; a first message to a new contact has no conversation yet and goes out untagged); \"pass\": \"<name>\" opens the url with <name>=<the chat's id on its channel> added, so the site can name the person back in its own events; \"pass_source\": \"<name>\" adds <name>=<where the chat came from> (a bot link's start parameter, an ad's ref; nothing when unknown); a \"web_app\" button takes \"pass\" and \"pass_source\" too (no track): they are written into its url when the message is sent. Only on channels that support buttons (Telegram bot accounts); can accompany at most one attachment, and when the text is too long for a media caption the buttons arrive with the text as a second message."
  4. Changed1 schema field changed
    • changedInput schema / properties / buttons / description
      Previous value: -"Inline reply buttons shown under the message, one per row (max 10). Each item is {\"label\": \"<visible button text>\"} plus exactly one target: \"value\" (a string sent back as a normal incoming message when tapped, defaults to the label, max 64 bytes), \"url\" (opens a link) or \"web_app\" (opens an https page as a Telegram Mini App). A \"url\" button may add \"track\": true: the tap is then counted for this conversation (analytics_link_clicks_v in analytics.query) and the person is sent on to the url; \"tag\": <ai_tag id> beside it also puts that tag on the CONVERSATION at the tap (a group's tag is any member's tap; a first message to a new contact has no conversation yet and goes out untagged); \"pass\": \"<name>\" opens the url with <name>=<the chat's id on its channel> added, so the site can name the person back in its own events. Only on channels that support buttons (Telegram bot accounts); can accompany at most one attachment, and when the text is too long for a media caption the buttons arrive with the text as a second message."New value: +"Inline reply buttons shown under the message, one per row (max 10). Each item is {\"label\": \"<visible button text>\"} plus exactly one target: \"value\" (a string sent back as a normal incoming message when tapped, defaults to the label, max 64 bytes), \"url\" (opens a link) or \"web_app\" (opens an https page as a Telegram Mini App). A \"url\" button may add \"track\": true: the tap is then counted for this conversation (analytics_link_clicks_v in analytics.query) and the person is sent on to the url; \"tag\": <ai_tag id> beside it also puts that tag on the CONVERSATION at the tap (a group's tag is any member's tap; a first message to a new contact has no conversation yet and goes out untagged); \"pass\": \"<name>\" opens the url with <name>=<the chat's id on its channel> added, so the site can name the person back in its own events; \"pass_source\": \"<name>\" adds <name>=<where the chat came from> (a bot link's start parameter, an ad's ref; nothing when unknown). Only on channels that support buttons (Telegram bot accounts); can accompany at most one attachment, and when the text is too long for a media caption the buttons arrive with the text as a second message."
  5. Changed1 schema field changed
    • changedInput schema / properties / mentions / description
      Previous value: -"People of a group chat to @-tag so the platform really notifies them (WhatsApp, Telegram groups). Each item names one member of THIS chat by one of: \"name\" (as shown in the chat), \"phone\" (international number) or \"entity_id\". If the text already holds \"@<name>\" that spot is the tag, otherwise \"@<name> \" is put in front of the text. A person who is not in the chat, or who matches several, refuses the whole send and lists the members. Without this parameter a \"@Name\" in the text of a group message tags the member it names in the same way, and an @-word that names nobody refuses the send (on Telegram it stays text: a typed @username is a link there). Not combinable with attachments or buttons, and not available while the agent sends drafts. Text may be empty: the tags alone are sent."New value: +"People of a group chat to @-tag so the platform really notifies them (WhatsApp, Telegram groups). Each item names one member of THIS chat by one of: \"name\" (as shown in the chat), \"phone\" (international number) or \"entity_id\". If the text already holds \"@<name>\" that spot is the tag, otherwise \"@<name> \" is put in front of the text. A person passed here who is not in the chat, or who matches several, refuses the whole send and lists the members. Without this parameter a \"@Name\" in the text of a group message tags the member it names in the same way; an @-word that names nobody, or several members, refuses the send on WhatsApp, while on Telegram the message goes out with that word as plain text and the result's \"warnings\" names it (it tagged nobody: check them and pass mentions). Not combinable with attachments or buttons, and not available while the agent sends drafts. Text may be empty: the tags alone are sent."
  6. Changed1 schema field changed
    • changedInput schema / properties / thread_id / description
      Previous value: -"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. To write to a phone number nobody has a thread with yet: 'whatsapp:+<number in international format>' writes to it from a personal WhatsApp account (from_account_id picks which one), 'whatsapp_business:+<number in international format>' opens a WhatsApp conversation from a WhatsApp Business API number (from_account_id picks which one; the first message must be a `template`), and 'sms:+<number>' texts it from a workspace phone number that has SMS turned on (from_account_id picks which one), landing in that number's conversation with the recipient, next to their calls. 'x:@<handle>' sends a first X direct message to that person from a connected X account; X refuses it when their inbox is closed to the sender. 'discord:<user id>' (the person's numeric Discord id) sends a first Discord DM from a connected Discord account, into the DM that exists with them or one opened for it; new DMs are limited per account and day, and refused in words with a retry_after when over. 'skool:user:<user id>' (optionally '@<community id>' after the id, when the two share several communities) sends a first message on Skool from a connected Skool account; a Skool post thread ('skool:<account>:post:<post id>') takes a comment instead. NEVER use a chat-type word (dm, group, channel, livechat, comment_thread) — those are category labels from the SITUATION block, not ids."New value: +"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. To write to a phone number nobody has a thread with yet: 'whatsapp:+<number in international format>' writes to it from a personal WhatsApp account (from_account_id picks which one), 'viber:+<number in international format>' writes to it from the workspace's own Viber number (from_account_id picks which one), 'whatsapp_business:+<number in international format>' opens a WhatsApp conversation from a WhatsApp Business API number (from_account_id picks which one; the first message must be a `template`), and 'sms:+<number>' texts it from a workspace phone number that has SMS turned on (from_account_id picks which one), landing in that number's conversation with the recipient, next to their calls. 'x:@<handle>' sends a first X direct message to that person from a connected X account; X refuses it when their inbox is closed to the sender. 'discord:<user id>' (the person's numeric Discord id) sends a first Discord DM from a connected Discord account, into the DM that exists with them or one opened for it; new DMs are limited per account and day, and refused in words with a retry_after when over. 'skool:user:<user id>' (optionally '@<community id>' after the id, when the two share several communities) sends a first message on Skool from a connected Skool account; a Skool post thread ('skool:<account>:post:<post id>') takes a comment instead. NEVER use a chat-type word (dm, group, channel, livechat, comment_thread) — those are category labels from the SITUATION block, not ids."
  7. Changed1 schema field changed
    • addedInput schema / properties / as_document
      Added value: +{
      +  "description": "Send image attachments as files (documents) instead of photos, so the channel does not recompress them (Telegram: full-quality PNG/JPEG with the original filename). A single image already goes as a file; several go as one album of files, after any photo attachments, with the caption on the first album. Ignored on channels that have no such distinction.",
      +  "type": "boolean"
      +}
  8. Changed2 schema fields changed
    • changedInput schema / properties / recipient_name / description
      Previous value: -"Name of person to send to (e.g., 'Jane', 'John'). Tool will auto-resolve channel. Optional if thread_id provided."New value: +"Name of a person already in contacts (e.g., 'Jane', 'John'). Tool will auto-resolve channel. Optional if thread_id provided. Not for a phone number: a new number goes in thread_id (see there)."
    • changedInput schema / properties / thread_id / description
      Previous value: -"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. To write to a phone number nobody has a thread with yet: 'whatsapp_business:+<number in international format>' opens a WhatsApp conversation from a WhatsApp Business API number (from_account_id picks which one; the first message must be a `template`), and 'sms:+<number>' texts it from a workspace phone number that has SMS turned on (from_account_id picks which one), landing in that number's conversation with the recipient, next to their calls. 'x:@<handle>' sends a first X direct message to that person from a connected X account; X refuses it when their inbox is closed to the sender. 'discord:<user id>' (the person's numeric Discord id) sends a first Discord DM from a connected Discord account, into the DM that exists with them or one opened for it; new DMs are limited per account and day, and refused in words with a retry_after when over. 'skool:user:<user id>' (optionally '@<community id>' after the id, when the two share several communities) sends a first message on Skool from a connected Skool account; a Skool post thread ('skool:<account>:post:<post id>') takes a comment instead. NEVER use a chat-type word (dm, group, channel, livechat, comment_thread) — those are category labels from the SITUATION block, not ids."New value: +"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. To write to a phone number nobody has a thread with yet: 'whatsapp:+<number in international format>' writes to it from a personal WhatsApp account (from_account_id picks which one), 'whatsapp_business:+<number in international format>' opens a WhatsApp conversation from a WhatsApp Business API number (from_account_id picks which one; the first message must be a `template`), and 'sms:+<number>' texts it from a workspace phone number that has SMS turned on (from_account_id picks which one), landing in that number's conversation with the recipient, next to their calls. 'x:@<handle>' sends a first X direct message to that person from a connected X account; X refuses it when their inbox is closed to the sender. 'discord:<user id>' (the person's numeric Discord id) sends a first Discord DM from a connected Discord account, into the DM that exists with them or one opened for it; new DMs are limited per account and day, and refused in words with a retry_after when over. 'skool:user:<user id>' (optionally '@<community id>' after the id, when the two share several communities) sends a first message on Skool from a connected Skool account; a Skool post thread ('skool:<account>:post:<post id>') takes a comment instead. NEVER use a chat-type word (dm, group, channel, livechat, comment_thread) — those are category labels from the SITUATION block, not ids."
  9. Changed1 schema field changed
    • changedInput schema / properties / buttons / description
      Previous value: -"Inline reply buttons shown under the message, one per row (max 10). Each item is {\"label\": \"<visible button text>\"} plus exactly one target: \"value\" (a string sent back as a normal incoming message when tapped, defaults to the label, max 64 bytes), \"url\" (opens a link) or \"web_app\" (opens an https page as a Telegram Mini App). A \"url\" button may add \"track\": true: the tap is then counted for this conversation (analytics_link_clicks_v in analytics.query) and the person is sent on to the url; \"tag\": <ai_tag id> beside it also puts that tag on the CONVERSATION at the tap (a group's tag is any member's tap; a first message to a new contact has no conversation yet and goes out untagged). Only on channels that support buttons (Telegram bot accounts); can accompany at most one attachment, and when the text is too long for a media caption the buttons arrive with the text as a second message."New value: +"Inline reply buttons shown under the message, one per row (max 10). Each item is {\"label\": \"<visible button text>\"} plus exactly one target: \"value\" (a string sent back as a normal incoming message when tapped, defaults to the label, max 64 bytes), \"url\" (opens a link) or \"web_app\" (opens an https page as a Telegram Mini App). A \"url\" button may add \"track\": true: the tap is then counted for this conversation (analytics_link_clicks_v in analytics.query) and the person is sent on to the url; \"tag\": <ai_tag id> beside it also puts that tag on the CONVERSATION at the tap (a group's tag is any member's tap; a first message to a new contact has no conversation yet and goes out untagged); \"pass\": \"<name>\" opens the url with <name>=<the chat's id on its channel> added, so the site can name the person back in its own events. Only on channels that support buttons (Telegram bot accounts); can accompany at most one attachment, and when the text is too long for a media caption the buttons arrive with the text as a second message."
  10. Changed2 schema fields changed
    • changedInput schema / properties / buttons / description
      Previous value: -"Inline reply buttons shown under the message, one per row (max 10). Each item is {\"label\": \"<visible button text>\"} plus exactly one target: \"value\" (a string sent back as a normal incoming message when tapped, defaults to the label, max 64 bytes), \"url\" (opens a link) or \"web_app\" (opens an https page as a Telegram Mini App). A \"url\" button may add \"track\": true: the tap is then counted for this conversation (analytics_link_clicks_v in analytics.query) and the person is sent on to the url. Only on channels that support buttons (Telegram bot accounts); can accompany at most one attachment, and when the text is too long for a media caption the buttons arrive with the text as a second message."New value: +"Inline reply buttons shown under the message, one per row (max 10). Each item is {\"label\": \"<visible button text>\"} plus exactly one target: \"value\" (a string sent back as a normal incoming message when tapped, defaults to the label, max 64 bytes), \"url\" (opens a link) or \"web_app\" (opens an https page as a Telegram Mini App). A \"url\" button may add \"track\": true: the tap is then counted for this conversation (analytics_link_clicks_v in analytics.query) and the person is sent on to the url; \"tag\": <ai_tag id> beside it also puts that tag on the CONVERSATION at the tap (a group's tag is any member's tap; a first message to a new contact has no conversation yet and goes out untagged). Only on channels that support buttons (Telegram bot accounts); can accompany at most one attachment, and when the text is too long for a media caption the buttons arrive with the text as a second message."
    • changedInput schema / properties / mentions / description
      Previous value: -"People of a group chat to @-tag so the platform really notifies them (WhatsApp, Telegram groups). Each item names one member of THIS chat by one of: \"name\" (as shown in the chat), \"phone\" (international number) or \"entity_id\". If the text already holds \"@<name>\" that spot is the tag, otherwise \"@<name> \" is put in front of the text. A person who is not in the chat, or who matches several, refuses the whole send and lists the members. A plain \"@Name\" typed without this notifies nobody. Not combinable with attachments or buttons, and not available while the agent sends drafts. Text may be empty: the tags alone are sent."New value: +"People of a group chat to @-tag so the platform really notifies them (WhatsApp, Telegram groups). Each item names one member of THIS chat by one of: \"name\" (as shown in the chat), \"phone\" (international number) or \"entity_id\". If the text already holds \"@<name>\" that spot is the tag, otherwise \"@<name> \" is put in front of the text. A person who is not in the chat, or who matches several, refuses the whole send and lists the members. Without this parameter a \"@Name\" in the text of a group message tags the member it names in the same way, and an @-word that names nobody refuses the send (on Telegram it stays text: a typed @username is a link there). Not combinable with attachments or buttons, and not available while the agent sends drafts. Text may be empty: the tags alone are sent."
  11. Changed1 schema field changed
    • changedInput schema / properties / thread_id / description
      Previous value: -"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. To write to a phone number nobody has a thread with yet: 'whatsapp_business:+<number in international format>' opens a WhatsApp conversation from a WhatsApp Business API number (from_account_id picks which one; the first message must be a `template`), and 'sms:+<number>' texts it from a workspace phone number that has SMS turned on (from_account_id picks which one), landing in that number's conversation with the recipient, next to their calls. 'x:@<handle>' sends a first X direct message to that person from a connected X account; X refuses it when their inbox is closed to the sender. 'discord:<user id>' (the person's numeric Discord id) sends a first Discord DM from a connected Discord account, into the DM that exists with them or one opened for it; new DMs are limited per account and day, and refused in words with a retry_after when over. NEVER use a chat-type word (dm, group, channel, livechat, comment_thread) — those are category labels from the SITUATION block, not ids."New value: +"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. To write to a phone number nobody has a thread with yet: 'whatsapp_business:+<number in international format>' opens a WhatsApp conversation from a WhatsApp Business API number (from_account_id picks which one; the first message must be a `template`), and 'sms:+<number>' texts it from a workspace phone number that has SMS turned on (from_account_id picks which one), landing in that number's conversation with the recipient, next to their calls. 'x:@<handle>' sends a first X direct message to that person from a connected X account; X refuses it when their inbox is closed to the sender. 'discord:<user id>' (the person's numeric Discord id) sends a first Discord DM from a connected Discord account, into the DM that exists with them or one opened for it; new DMs are limited per account and day, and refused in words with a retry_after when over. 'skool:user:<user id>' (optionally '@<community id>' after the id, when the two share several communities) sends a first message on Skool from a connected Skool account; a Skool post thread ('skool:<account>:post:<post id>') takes a comment instead. NEVER use a chat-type word (dm, group, channel, livechat, comment_thread) — those are category labels from the SITUATION block, not ids."
  12. Changed1 schema field changed
    • changedInput schema / properties / thread_id / description
      Previous value: -"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. To write to a phone number nobody has a thread with yet: 'whatsapp_business:+<number in international format>' opens a WhatsApp conversation from a WhatsApp Business API number (from_account_id picks which one; the first message must be a `template`), and 'sms:+<number>' texts it from a workspace phone number that has SMS turned on (from_account_id picks which one), landing in that number's conversation with the recipient, next to their calls. 'x:@<handle>' sends a first X direct message to that person from a connected X account; X refuses it when their inbox is closed to the sender. NEVER use a chat-type word (dm, group, channel, livechat, comment_thread) — those are category labels from the SITUATION block, not ids."New value: +"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. To write to a phone number nobody has a thread with yet: 'whatsapp_business:+<number in international format>' opens a WhatsApp conversation from a WhatsApp Business API number (from_account_id picks which one; the first message must be a `template`), and 'sms:+<number>' texts it from a workspace phone number that has SMS turned on (from_account_id picks which one), landing in that number's conversation with the recipient, next to their calls. 'x:@<handle>' sends a first X direct message to that person from a connected X account; X refuses it when their inbox is closed to the sender. 'discord:<user id>' (the person's numeric Discord id) sends a first Discord DM from a connected Discord account, into the DM that exists with them or one opened for it; new DMs are limited per account and day, and refused in words with a retry_after when over. NEVER use a chat-type word (dm, group, channel, livechat, comment_thread) — those are category labels from the SITUATION block, not ids."
  13. Changed1 schema field changed
    • addedInput schema / properties / mentions
      Added value: +{
      +  "description": "People of a group chat to @-tag so the platform really notifies them (WhatsApp, Telegram groups). Each item names one member of THIS chat by one of: \"name\" (as shown in the chat), \"phone\" (international number) or \"entity_id\". If the text already holds \"@<name>\" that spot is the tag, otherwise \"@<name> \" is put in front of the text. A person who is not in the chat, or who matches several, refuses the whole send and lists the members. A plain \"@Name\" typed without this notifies nobody. Not combinable with attachments or buttons, and not available while the agent sends drafts. Text may be empty: the tags alone are sent.",
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  14. Changed1 schema field changed
    • changedInput schema / properties / thread_id / description
      Previous value: -"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. To write to a phone number nobody has a thread with yet: 'whatsapp_business:+<number in international format>' opens a WhatsApp conversation from a WhatsApp Business API number (from_account_id picks which one; the first message must be a `template`), and 'sms:+<number>' texts it from a workspace phone number that has SMS turned on (from_account_id picks which one), landing in that number's conversation with the recipient, next to their calls. NEVER use a chat-type word (dm, group, channel, livechat, comment_thread) — those are category labels from the SITUATION block, not ids."New value: +"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. To write to a phone number nobody has a thread with yet: 'whatsapp_business:+<number in international format>' opens a WhatsApp conversation from a WhatsApp Business API number (from_account_id picks which one; the first message must be a `template`), and 'sms:+<number>' texts it from a workspace phone number that has SMS turned on (from_account_id picks which one), landing in that number's conversation with the recipient, next to their calls. 'x:@<handle>' sends a first X direct message to that person from a connected X account; X refuses it when their inbox is closed to the sender. NEVER use a chat-type word (dm, group, channel, livechat, comment_thread) — those are category labels from the SITUATION block, not ids."
  15. Changed1 schema field changed
    • changedInput schema / properties / from_account_id / description
      Previous value: -"Which of the workspace's accounts on this channel SENDS the message, i.e. the number or handle the recipient sees. Only meaningful when starting a NEW conversation — an existing thread already belongs to an account and that one is used. OMIT and the platform picks the most recently active account, which is a coin flip in a workspace with several numbers: pass it whenever one of them must not be used to open conversations (a personal line, or one under a spam restriction). An account that is not active in this workspace is refused, never silently swapped."New value: +"Which of the workspace's accounts on this channel SENDS the message, i.e. the number or handle the recipient sees. A numeric thread_id is one conversation on one account: naming a different account for it is refused. With a channel_ref or recipient_username, the conversation ON THIS ACCOUNT is used, or opened where the channel can start one; if it has none, the send is refused rather than made from another account. OMIT and the platform picks the most recently active account, which is a coin flip in a workspace with several numbers: pass it whenever one of them must not be used to open conversations (a personal line, or one under a spam restriction). An account that is not active in this workspace is refused, never silently swapped."
  16. Changed1 schema field changed
    • changedInput schema / properties / buttons / description
      Previous value: -"Inline reply buttons shown under the message, one per row (max 10). Each item is {\"label\": \"<visible button text>\"} plus exactly one target: \"value\" (a string sent back as a normal incoming message when tapped, defaults to the label, max 64 bytes), \"url\" (opens a link) or \"web_app\" (opens an https page as a Telegram Mini App). Only on channels that support buttons (Telegram bot accounts); can accompany at most one attachment, and when the text is too long for a media caption the buttons arrive with the text as a second message."New value: +"Inline reply buttons shown under the message, one per row (max 10). Each item is {\"label\": \"<visible button text>\"} plus exactly one target: \"value\" (a string sent back as a normal incoming message when tapped, defaults to the label, max 64 bytes), \"url\" (opens a link) or \"web_app\" (opens an https page as a Telegram Mini App). A \"url\" button may add \"track\": true: the tap is then counted for this conversation (analytics_link_clicks_v in analytics.query) and the person is sent on to the url. Only on channels that support buttons (Telegram bot accounts); can accompany at most one attachment, and when the text is too long for a media caption the buttons arrive with the text as a second message."
  17. Changed1 schema field changed
    • changedInput schema / properties / thread_id / description
      Previous value: -"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. To write to a phone number nobody has a thread with yet: 'whatsapp_business:+<number in international format>' opens a WhatsApp conversation from a WhatsApp Business API number (from_account_id picks which one; the first message must be a `template`), and 'sms:+<number>' texts it from a workspace phone number that has SMS turned on (from_account_id picks which one), landing in that number's conversation with the recipient, next to their calls. NEVER use a chat-type word (dm, group, channel, livechat) — those are category labels from the SITUATION block, not ids."New value: +"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. To write to a phone number nobody has a thread with yet: 'whatsapp_business:+<number in international format>' opens a WhatsApp conversation from a WhatsApp Business API number (from_account_id picks which one; the first message must be a `template`), and 'sms:+<number>' texts it from a workspace phone number that has SMS turned on (from_account_id picks which one), landing in that number's conversation with the recipient, next to their calls. NEVER use a chat-type word (dm, group, channel, livechat, comment_thread) — those are category labels from the SITUATION block, not ids."
  18. Changed3 schema fields changed
    • changedInput schema / properties / template / description
      Previous value: -"WhatsApp Business API only. An approved template to send instead of free text, in Meta's shape: {name, language, components:[{type:'body', parameters:[{type:'text', text:...}]}, ...]}; `language` may be the code as a string ('en_US') or Meta's {code:'en_US'}. Required when the 24-hour window of the conversation is closed (the send answers WINDOW_EXPIRED otherwise). Read the approved templates and their variables with channels.list(account_id=...)."New value: +"WhatsApp Business API only. An approved template to send instead of free text, in Meta's shape: {name, language, components:[{type:'body', parameters:[{type:'text', text:...}]}, ...]}; `language` is the code as a string ('en_US'). Required when the 24-hour window of the conversation is closed (the send answers WINDOW_EXPIRED otherwise). Read the approved templates and their variables with channels.list(account_id=...)."
    • addedInput schema / properties / template / properties
      Added value: +{
      +  "components": {
      +    "description": "Variable values per component, in Meta's shape.",
      +    "items": {
      +      "properties": {
      +        "parameters": {
      +          "items": {
      +            "properties": {
      +              "text": {
      +                "description": "The value of this variable.",
      +                "type": "string"
      +              },
      +              "type": {
      +                "description": "'text'.",
      +                "type": "string"
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "type": {
      +          "description": "'body', 'header' or 'button'.",
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "type": "array"
      +  },
      +  "language": {
      +    "description": "Template language code, e.g. 'en_US'.",
      +    "type": "string"
      +  },
      +  "name": {
      +    "description": "Template name as approved at Meta.",
      +    "type": "string"
      +  }
      +}
    • changedInput schema / properties / thread_id / description
      Previous value: -"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. To text a phone number, pass 'sms:+<number in international format>': the message goes out from a workspace phone number that has SMS turned on (from_account_id picks which one) and lands in that number's conversation with the recipient, next to their calls. NEVER use a chat-type word (dm, group, channel, livechat) — those are category labels from the SITUATION block, not ids."New value: +"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. To write to a phone number nobody has a thread with yet: 'whatsapp_business:+<number in international format>' opens a WhatsApp conversation from a WhatsApp Business API number (from_account_id picks which one; the first message must be a `template`), and 'sms:+<number>' texts it from a workspace phone number that has SMS turned on (from_account_id picks which one), landing in that number's conversation with the recipient, next to their calls. NEVER use a chat-type word (dm, group, channel, livechat) — those are category labels from the SITUATION block, not ids."
  19. Changed1 schema field changed
    • addedInput schema / properties / template
      Added value: +{
      +  "description": "WhatsApp Business API only. An approved template to send instead of free text, in Meta's shape: {name, language, components:[{type:'body', parameters:[{type:'text', text:...}]}, ...]}; `language` may be the code as a string ('en_US') or Meta's {code:'en_US'}. Required when the 24-hour window of the conversation is closed (the send answers WINDOW_EXPIRED otherwise). Read the approved templates and their variables with channels.list(account_id=...).",
      +  "type": "object"
      +}
  20. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  21. Changed1 schema field changed
    • changedInput schema / properties / thread_id / description
      Previous value: -"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. To text a phone number that has no thread yet, pass 'sms:+<number in international format>' (the workspace needs a phone number with SMS turned on; from_account_id picks which one). NEVER use a chat-type word (dm, group, channel, livechat) — those are category labels from the SITUATION block, not ids."New value: +"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. To text a phone number, pass 'sms:+<number in international format>': the message goes out from a workspace phone number that has SMS turned on (from_account_id picks which one) and lands in that number's conversation with the recipient, next to their calls. NEVER use a chat-type word (dm, group, channel, livechat) — those are category labels from the SITUATION block, not ids."
  22. Changed1 schema field changed
    • changedInput schema / properties / thread_id / description
      Previous value: -"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. NEVER use a chat-type word (dm, group, channel, livechat) — those are category labels from the SITUATION block, not ids."New value: +"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. To text a phone number that has no thread yet, pass 'sms:+<number in international format>' (the workspace needs a phone number with SMS turned on; from_account_id picks which one). NEVER use a chat-type word (dm, group, channel, livechat) — those are category labels from the SITUATION block, not ids."
  23. Added
  24. Removed
  25. Changed1 schema field changed
    • addedInput schema / properties / recipient_username
      Added value: +{
      +  "description": "Telegram @username to message (e.g. '@some_username'). Use this for a Telegram user NOT yet in contacts — it resolves the handle, adds the contact, and creates the thread. Telegram only; for existing contacts prefer thread_id or recipient_name.",
      +  "type": "string"
      +}
  26. Changed8 schema fields changed
    • changedInput schema / properties / attachments / description
      Previous value: -"Array of integer file IDs to send as attachments (images, documents, any files). Get file IDs from collections.list_files (field `file_id`), workspace.search with scope=['files'] (field `file_id`), or files.search. Example: [302237]. The file must already exist in the workspace (status=ready) — no separate upload step needed. When attachments are provided, `text` becomes optional (a caption can be included alongside)."New value: +"Array of integer file IDs to send as attachments (images, documents, any files). Get file IDs from collections.list_files (field `file_id`), search.files (field `file_id`), or files.search. Example: [302237]. The file must already exist in the workspace (status=ready) — no separate upload step needed. When attachments are provided, `text` becomes optional (a caption can be included alongside)."
    • removedInput schema / properties / bcc
      Removed value: -{
      -  "description": "Email addresses to BCC (blind carbon copy). Only for email channel.",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • removedInput schema / properties / cc
      Removed value: -{
      -  "description": "Email addresses to CC (carbon copy). Only for email channel.",
      -  "items": {
      -    "type": "string"
      -  },
      -  "type": "array"
      -}
    • removedInput schema / properties / channel
      Removed value: -{
      -  "description": "Channel hint (e.g. 'telegram'). Required when using recipient_username. Only 'telegram' is currently accepted for handle-based routing.",
      -  "type": "string"
      -}
    • removedInput schema / properties / recipient_email
      Removed value: -{
      -  "description": "Email address to send to (e.g., 'john@example.com'). Creates new email thread. Only for email channel.",
      -  "type": "string"
      -}
    • removedInput schema / properties / recipient_username
      Removed value: -{
      -  "description": "Telegram @handle (e.g. '@smartdeveloper' or 'smartdeveloper'). Resolves or opens a DM without needing a DB thread_id. Requires channel='telegram'. Only Telegram supported in this release.",
      -  "type": "string"
      -}
    • removedInput schema / properties / subject
      Removed value: -{
      -  "description": "Email subject line. Required for new emails, optional for replies (auto-generates 'Re: ...').",
      -  "type": "string"
      -}
    • changedInput schema / properties / thread_id / description
      Previous value: -"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from threads.list / workspace.search, or (b) a channel_ref like 'telegram:-12345'. NEVER use a chat-type word (dm, group, channel, livechat) — those are category labels from the SITUATION block, not ids."New value: +"Target thread. OMIT to reply in the same chat you received the triggering message from — the backend defaults to the current thread. Pass an explicit value ONLY to reply in a DIFFERENT thread, and only use: (a) a numeric DB thread id from search.threads, or (b) a channel_ref like 'telegram:-12345'. NEVER use a chat-type word (dm, group, channel, livechat) — those are category labels from the SITUATION block, not ids."
  27. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only flag destructiveHint/openWorldHint/idempotent=false; the description adds substantive behavior beyond that: sends are refused when the WhatsApp 24-hour window is closed (WINDOW_EXPIRED), mentions that match nobody refuse the whole send on WhatsApp while Telegram degrades to plain text with a warning, and new Discord DMs are rate-limited with a retry_after. It also discloses the trace_id consequence — filing the message as an agent reply rather than pausing the agent — which no annotation conveys.

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?

Six sentences, front-loaded with the core action followed by channel support, LinkedIn comment semantics, topic behavior, and attachments — each sentence carries a distinct capability rather than padding. It is dense and longer than typical, but no sentence is filler; the LinkedIn comment-thread and topic_id sentences are arguably the most compressible.

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 17-parameter tool with no output schema and no required parameters, the description covers the high-risk paths an agent must get right: attachments without text, template-required windows, private replies, and thread resolution. The complex `buttons` and `mentions` parameters are left entirely to their very detailed schema entries, which is a reasonable division given the 100% coverage, though the description's single line on buttons understates that surface.

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?

With 100% schema description coverage the baseline is 3, and the description does add cross-parameter semantics the schema does not state as a unit: text becomes optional once attachments are present, and attachment file IDs must come from collections.list_files, search.files, or files.search. It also explains that recipient_name and thread_id are alternatives for resolution. Much of the per-parameter detail duplicates the already-rich schema text, so it is not a full 5.

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 opening sentence names a specific verb and resource ('Send a message to a thread, channel, or contact') and lists supported channels, so the core action is unmistakable. It is slightly muddied by claiming Email support while a sibling named messages_send_email exists, leaving the agent unsure which tool handles email; the description never names that sibling or draws the boundary.

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?

It states when to omit thread_id (defaults to the triggering chat), when to pass it (only for a different thread), and gives the exact channel_ref forms per channel including the requirement that a WhatsApp Business first message be a template. It also states when topic_id is unnecessary because a reply stays in its topic, and when private_reply must be omitted for a normal send — explicit when/when-not guidance throughout.

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.