Skip to main content
Glama
Sign In

DialogBrain

by com.dialogbrain.api
OverviewDiscussionsAdmin

group_join

Join a group and start syncing its messages to your inbox. The group must be in your discovery list (use group.search or group.add first).

What this does:

  • Joins the group on Telegram or WhatsApp (WhatsApp: personal QR-paired accounts, by the invite link given to group.add; a group whose admins must approve members is only requested, not joined)

  • Creates a thread in your inbox for syncing messages

  • Optionally enables AI auto-reply drafts

Returns: success, thread_id, auto_reply_enabled.

Input Schema

NameRequiredDescriptionDefault
group_idYesGroup to act on. Accepts either the discovered-group id from group.search / group.list / group.add, or the platform's own group id (a Telegram chat id like -1001234567890, or a WhatsApp group JID ending in @g.us).
account_idNoWhich of the workspace's accounts on this channel acts (from channels.list). OMIT to use the account the group belongs to.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
enable_auto_replyNoEnable AI auto-reply drafts for messages in this group. Drafts can be reviewed and sent manually. Default: false (large public groups would otherwise generate drafts for every incoming message).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / group_id / description
      Previous value: -"Group to act on. Accepts either the discovered-group id from group.search / group.list, or the platform's own group id (e.g. a Telegram chat id like -1001234567890)."New value: +"Group to act on. Accepts either the discovered-group id from group.search / group.list / group.add, or the platform's own group id (a Telegram chat id like -1001234567890, or a WhatsApp group JID ending in @g.us)."
    • changedInput schema / properties / group_id / type
      Previous value: -"integer"New value: +"string"
  2. Changed1 schema field changed
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Which of the workspace's accounts on this channel acts (from channels.list). OMIT to use the account the group belongs to.",
+  "type": "integer"
+}
  3. Added
  4. Removed
  5. Changed2 schema fields changed
    • removedInput schema / properties / enable_auto_reply / default
      Removed value: -true
    • changedInput schema / properties / enable_auto_reply / description
      Previous value: -"Enable AI auto-reply drafts for messages in this group. Drafts can be reviewed and sent manually. Default: true."New value: +"Enable AI auto-reply drafts for messages in this group. Drafts can be reviewed and sent manually. Default: false (large public groups would otherwise generate drafts for every incoming message)."
  6. Added

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (which only say non-read-only, non-idempotent, non-destructive), the description discloses the important asymmetric behavior: on WhatsApp, admin-approval groups are only *requested*, not joined. It also lists the return fields. It does not cover failure modes or what happens if the group is already joined, though idempotentHint=false hints at that.

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?

Front-loaded one-line summary followed by a short bulleted breakdown and an explicit Returns line. No filler, and each bullet covers a distinct behavioral fact.

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 4-parameter mutation tool with no output schema, the description covers preconditions, per-platform behavior, side effects, and return fields. Missing only edge-case behavior such as re-joining an already-joined group or authorization requirements.

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 description coverage is 100%, so the schema already carries the parameter semantics, and the description adds little beyond reiterating that auto-reply is optional. It does add context that the WhatsApp invite link from group.add is what gets used, which is marginal added value; baseline 3 is appropriate.

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?

Opens with a specific verb+resource ('Join a group') and immediately states the side effect ('start syncing its messages to your inbox'), then enumerates the three concrete outcomes including the platform join, thread creation, and optional auto-reply. It is clearly distinguishable from siblings like group_add and group_search.

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 states the precondition ('The group must be in your discovery list') and names the concrete alternatives to satisfy it ('use group.search or group.add first'). An agent that fails this precondition knows exactly which sibling to call.

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

All DialogBrain toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources