Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

group_promote_admin

Promote a member to admin in an existing group on Telegram or WhatsApp.

What this does:

  • Gives the specified member admin status in the group

  • On Telegram, this grants visibility of all group messages (even if not a bot)

  • Defaults to minimal/empty rights; specify custom rights if needed

Returns: success, chat_id, member.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memberYesThe member to promote (format depends on channel: @username on Telegram, phone on WhatsApp)
rightsNoOptional admin rights dict (Telegram-specific). If not provided, defaults to minimal/admin status only. Example: {"post_messages": true, "edit_messages": true}
channelYesChannel where the group exists (e.g., 'telegram', 'whatsapp')
chat_idYesID of the group/channel where the member will be promoted. 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

A3.7/5.0
Behavior4/5

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

Annotations already declare it is a non-readonly, non-destructive, non-idempotent mutation. Beyond that the description discloses a genuinely non-obvious side effect: on Telegram promotion grants visibility of all group messages even for non-bots, plus the minimal-rights default. It omits permission requirements and whether the change is reversible.

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 one-line purpose, then a tight bullet list and a returns line. Slight redundancy between the opening line and the first bullet, but nothing wasted.

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 non-idempotent mutation with no output schema, the description covers the effect, the platform-specific side effect, the rights default, and the return fields. Missing only permission/auth prerequisites needed to call it successfully.

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 all five params including channel-dependent member formats and the rights example. The description adds only the rights-default nuance, which is already partly in the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first line gives a specific verb (promote) and resource (member to admin in an existing group) and names the two supported channels. It does not distinguish itself from near-neighbors like group_admins or group_add_member, so an agent must infer which sibling applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Defaults to minimal/empty rights; specify custom rights if needed' is real usage guidance for the optional rights param. However, there is no statement of when to prefer this over group_admins/group_moderate, no prerequisites (e.g., caller must already be admin), and no exclusions.

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