Skip to main content
Glama
Sign In

DialogBrain

by com.dialogbrain.api
OverviewDiscussionsAdmin

group_add

Add a specific group to your discovery list by @username or invite link (Telegram t.me/..., WhatsApp chat.whatsapp.com/...). Nothing is joined yet: run group.join with the returned id to join and start syncing.

Groups and channels only — this does NOT add an individual person/contact. To add a person by @username (e.g. a customer or lead), use contacts.discover then contacts.sync instead.

When to use:

  • You already know the group's @username or invite link

  • Adding a known group without searching

Returns: group metadata including id, title, member_count.

Input Schema

NameRequiredDescriptionDefault
linkYesThe group's @username or invite link (e.g. '@phuket', 't.me/...' or 'https://chat.whatsapp.com/<code>')
channelYesChannel the group is on ('telegram' or 'whatsapp'; WhatsApp needs a personal QR-paired account, not the Business API)
account_idNoWhich of the workspace's accounts on this channel acts (from channels.list). OMIT to use the workspace's default account.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / channel / description
      Previous value: -"Channel the group is on (e.g. 'telegram')"New value: +"Channel the group is on ('telegram' or 'whatsapp'; WhatsApp needs a personal QR-paired account, not the Business API)"
    • changedInput schema / properties / link / description
      Previous value: -"The group's @username or invite link (e.g. '@phuket' or 't.me/...')"New value: +"The group's @username or invite link (e.g. '@phuket', 't.me/...' or 'https://chat.whatsapp.com/<code>')"
  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 workspace's default account.",
+  "type": "integer"
+}
  3. Added
  4. Removed
  5. Added

TDQS

A4.3/5.0
Behavior4/5

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

The key behavioral trait is disclosed beyond the annotations: adding to the discovery list does not join anything, and group.join must be called with the returned id to join and sync. Annotations already cover the non-destructive/non-idempotent profile, and the description adds the two-step flow and return contents, though it omits permission/account requirements and what happens when a group is added twice.

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 the action and the critical "nothing is joined yet" caveat, then a compact when-to-use list and a return summary. Slightly verbose in repeating the link formats already in the schema, but every section is scannable and goal-directed.

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, non-destructive add operation with no output schema, the description covers the follow-up step and states the return shape (id, title, member_count). It leaves authentication/account-selection context to the schema, which is acceptable, but a note on permission prerequisites or duplicate handling would close the remaining gap.

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 coverage is 100%, so link, channel, account_id, and in_workspace are already documented, including the WhatsApp QR-pairing note. The description only restates the accepted formats (@username, t.me/..., chat.whatsapp.com/...) that the schema already provides, so it adds no meaning beyond structured data — baseline 3 applies.

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?

States a specific verb and resource ("Add a specific group to your discovery list") and immediately scopes it to groups/channels with @username or invite link input. It distinguishes itself from group.join (joining) and from contacts.discover/contacts.sync (adding individuals), so an agent can separate it from siblings without opening schemas.

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 names the when-to-use condition ("You already know the group's @username or invite link") and exclusions ("this does NOT add an individual person/contact"). It also routes the agent to concrete alternatives: group.join for joining and contacts.discover/contacts.sync for people.

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