Skip to main content
Glama

send_group_attachment

Send files such as photos, videos, documents, or audio to a Signal group in a single encrypted message. Supports view-once media and optional caption.

Instructions

Send one or more files (photos, videos, documents, audio) to a Signal group in a single message. All current group members receive the attachment via the normal Signal encrypted delivery pipeline. Provide path for a single file or paths for multiple files sent together in one message. Set view_once=true so each member can only open the media once before it disappears — ideal for sensitive images; does not apply to document types. The file must exist and be readable on the local filesystem; non-existent paths return an error. Use list_groups to obtain the group_id. Use when sharing a file with a group chat. Do NOT use for direct messages — use send_attachment instead. Do NOT use when you only want to send text — use send_group_message instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYesGroup ID (get from list_groups)
pathNoSingle file path (absolute, relative, or ~/path)
pathsNoMultiple file paths to send as one message
captionNoOptional caption text shown below the attachment
view_onceNoSend as view-once media — each recipient can only view it once

Implementation Reference

  • The `send_group_attachment` method on SignalClient — the core handler that sends one or more files to a Signal group via JSON-RPC. Accepts group_id, path(s), optional caption, and view_once flag. Resolves file paths, builds params with groupId+attachment, calls the 'send' RPC method, and persists the sent message to the local store.
    async def send_group_attachment(
        self,
        group_id: str,
        path: str | list[str],
        caption: str = "",
        view_once: bool = False,
    ) -> SendResult:
        await self._rate_limiter.acquire()
        paths = [path] if isinstance(path, str) else path
        resolved = [str(Path(p).expanduser().resolve()) for p in paths]
        params: dict = {"groupId": group_id, "attachment": resolved}
        if caption:
            params["message"] = caption
        if view_once:
            params["viewOnce"] = True
        result = await self._rpc("send", params)
        ts = result.get("timestamp", int(time.time() * 1000))
        await asyncio.to_thread(_store.save_message, Message(
            id=f"sent_{ts}_{group_id}",
            sender=self.account,
            body=caption,
            timestamp=datetime.fromtimestamp(ts / 1000),
            group_id=group_id,
            is_read=True,  # sent by us, already "read"
        ))
        return SendResult(timestamp=ts, recipient=group_id, success=True)
  • The MCP Tool definition for 'send_group_attachment', including its description and inputSchema with properties: group_id (required), path, paths, caption, view_once.
    Tool(
        name="send_group_attachment",
        description=(
            "Send one or more files (photos, videos, documents, audio) to a Signal group in a single message. "
            "All current group members receive the attachment via the normal Signal encrypted delivery pipeline. "
            "Provide path for a single file or paths for multiple files sent together in one message. "
            "Set view_once=true so each member can only open the media once before it disappears — "
            "ideal for sensitive images; does not apply to document types. "
            "The file must exist and be readable on the local filesystem; non-existent paths return an error. "
            "Use list_groups to obtain the group_id. "
            "Use when sharing a file with a group chat. "
            "Do NOT use for direct messages — use send_attachment instead. "
            "Do NOT use when you only want to send text — use send_group_message instead."
        ),
        inputSchema={
            "type": "object",
            "properties": {
                "group_id": {"type": "string", "description": "Group ID (get from list_groups)"},
                "path": {"type": "string", "description": "Single file path (absolute, relative, or ~/path)"},
                "paths": {"type": "array", "items": {"type": "string"}, "description": "Multiple file paths to send as one message"},
                "caption": {"type": "string", "description": "Optional caption text shown below the attachment", "default": ""},
                "view_once": {"type": "boolean", "description": "Send as view-once media — each recipient can only view it once", "default": False},
            },
            "required": ["group_id"],
        },
    ),
  • The call_tool handler branch for 'send_group_attachment' — extracts path_arg, validates required group_id, calls client.send_group_attachment, and returns JSON result.
    elif name == "send_group_attachment":
        path_arg = arguments.get("paths") or arguments.get("path")
        if not path_arg:
            return _err("Either path or paths is required")
        result = await client.send_group_attachment(
            arguments["group_id"],
            path_arg,
            caption=arguments.get("caption", ""),
            view_once=arguments.get("view_once", False),
        )
        return _ok({"status": "sent", "timestamp": result.timestamp})
  • Required parameter validation entry for 'send_group_attachment' — specifies that 'group_id' is required.
    "send_group_attachment":["group_id"],
  • The SendResult dataclass returned by send_group_attachment (and other send methods), containing timestamp, recipient, success, and error fields.
    @dataclass
    class SendResult:
        timestamp: int
        recipient: str
        success: bool
        error: str | None = None
Behavior4/5

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

Despite no annotations, the description covers key behaviors: encrypted delivery, view_once limitation (not for documents), file must exist and be readable, and that multiple files can be sent together. Lacks mention of rate limits or confirmation, but reasonable for this tool.

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?

Front-loaded with core purpose, then provides usage details and differing conditions. Every sentence adds value, though slightly verbose; overall well-structured and clear.

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?

Thorough for a file-sending tool: covers prerequisites, single vs multiple files, view_once caveat, file existence requirement, and explicit usage boundaries with sibling tools. No obvious gaps.

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?

Schema already has 100% description coverage. The description adds value by explaining path vs paths distinction, view_once behavior (ideal for sensitive images, not for documents), and error on missing file, going beyond the schema.

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 files to a Signal group, specifies file types (photos, videos, documents, audio), and distinguishes from siblings by naming send_attachment and send_group_message.

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?

Explicitly tells when to use (sharing files with a group) and when not (direct messages or text only), with alternatives provided. Also instructs to use list_groups for group_id.

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