Skip to main content
Glama

send_group_message

Send an end-to-end encrypted text message to a Signal group. Supports @mentions and quoting, returning a timestamp for reactions or edits.

Instructions

Send a text message to a Signal group. The message is delivered end-to-end encrypted to all group members. Returns the sent timestamp, which can be used as target_timestamp for react_to_message or edit_message. To @mention a member, include their name in the message text and pass a mentions list where each entry has start (character index of the mention in the text), length (character count), and author (E.164 phone number). To reply/quote a message, provide quote_author (sender's phone number) and quote_timestamp (from get_conversation). Use list_groups to get group_id values. Use send_group_attachment to send files or images to a group. Do NOT use for direct messages to a contact — use send_message instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYesGroup ID (from list_groups)
messageYesMessage text to send
mentionsNoList of @mentions. Each item: {start: character offset of the mention in the message, length: character count of the mention, author: E.164 phone number of the mentioned member}. Example: message='Hello @Alice', mentions=[{start:6,length:6,author:'+1234567890'}]
quote_authorNoPhone number (E.164) of the author of the message being quoted
quote_timestampNoTimestamp of the quoted message (from get_conversation)
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses encryption, return value (timestamp) usable for other actions, and how mentions/quotes work. Could be improved by mentioning delivery guarantees or error handling, but still adds valuable behavioral context beyond purpose.

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?

Description is well-structured, front-loaded with core purpose, then encryption, then return value, then advanced features, then exclusions. Every sentence is informative and no waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description covers return value usage. It addresses all 5 parameters with usage patterns, dependencies (list_groups, get_conversation), and differentiation from siblings. Complete for agent decision-making.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 100% schema coverage, the description adds significant meaning: explains mentions structure with example, connects quote parameters to get_conversation, and clarifies which parameters are tied to other tools. Goes far beyond schema descriptions.

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?

The description clearly states the tool sends a text message to a Signal group, specifies end-to-end encryption, and distinguishes itself from related tools like send_message (for direct messages) and send_group_attachment (for files).

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?

Provides explicit when-to-use guidance, including not using for direct messages, instructions for mentions and quoting, and references to list_groups and get_conversation for prerequisites. Clearly explains alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/googlarz/signal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server