Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

group_get_invite_link

Get an invite link for an existing group (Telegram, WhatsApp).

What this does:

  • Telegram: mints a FRESH link (e.g. t.me/+...) on every call; previously issued links stay valid

  • WhatsApp: returns the group's EXISTING link, the same one each time. Do not describe it to anyone as newly issued

  • Requires the connected account to be the group's owner or an admin with invite rights

When to use:

  • A member can't be added directly because their privacy settings block invites (group.add_member fails with a privacy error) — send them this link instead

  • Onboarding people to a private group

Returns: success, chat_id, invite_link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYesChannel where the group exists (e.g., 'telegram')
chat_idYesID of the group/channel to export an invite link for. Group id exactly as `group.list` reports it: a signed numeric id on Telegram, or a JID ending in @g.us on WhatsApp. A WhatsApp group has no numeric id, so this is a string either way. Read it from `group.list`; never compose one.
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. 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"
+}
  2. Added
  3. Removed
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations mark it non-readonly and non-idempotent, and the description explains exactly why: Telegram mints a NEW link each call while prior links remain valid, WhatsApp returns the existing link (with a caution not to describe it as new). It also states the owner/admin-with-invite-rights requirement and the return fields — behavior beyond what the annotations convey.

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-loads the one-line purpose, then scannable 'What this does' / 'When to use' / 'Returns' sections. Every sentence carries distinct information with no filler.

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?

Covers platform-specific behavior, authorization prerequisites, usage triggers, and return shape. With no output schema, the explicit 'Returns: success, chat_id, invite_link' line closes the remaining gap, leaving nothing an agent needs missing.

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 documents chat_id, channel, and in_workspace thoroughly (including the 'never compose an ID' caveat). The description adds no parameter-level meaning beyond the schema, so the 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?

Specific verb+resource ('Get an invite link for an existing group') with platform scope (Telegram, WhatsApp) stated up front. An agent can immediately tell this apart from group_add_member or group_join without opening any schema.

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?

The 'When to use' block gives explicit triggering conditions: privacy settings blocking direct adds (add_member fails with a privacy error) and onboarding to a private group. It effectively routes the agent away from group_add_member toward this tool in a concrete failure scenario.

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