Skip to main content
Glama
Sign In
telegram-mcp

telegram-mcp

by dikaglorya
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Promote / demote an admin

telegram_promote_admin

Grant or revoke admin rights for a Telegram chat member using moderator, full, or none presets, with an optional custom title.

Instructions

Grant or revoke admin rights for a member. preset: 'moderator' (default, can delete and ban), 'full' (everything except anonymous), 'none' (demote). Optional custom title (rank).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chat": "<chat>",
      "user": "<user>"
    },
    "name": "telegram_promote_admin"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes
rankNo
userYes
presetNomoderator

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish that this is not read-only and is open-world. The description adds useful behavioral detail about what 'moderator', 'full', and 'none' do, but it omits important operational context such as required permissions, whether changes are immediately effective, and any irreversible or sensitive effects.

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?

Two sentences, front-loaded with the tool's action and followed by essential preset semantics. There is no wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter admin mutation with no output schema and minimal annotations, the description leaves significant gaps: required chat/user semantics are undocumented, and permission prerequisites or failure conditions are not described. It covers preset behavior well but is not complete enough for safe invocation by an agent unfamiliar with Telegram identifiers.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It explains the preset enum values and describes rank as an optional custom title, but it does not explain the required chat and user parameters or their expected identifier formats.

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 description states a specific verb and resource: granting or revoking admin rights for a member, and the preset 'none' makes demotion explicit. It is clear but does not contrast itself with adjacent tools such as telegram_kick_member or telegram_chat_admins.

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

Usage Guidelines4/5

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

It gives clear context for when to use the tool: granting or revoking admin rights. The preset explanations also clarify the intended effect of each mode, though it does not state prerequisites such as requiring the caller to be an owner/admin or name alternatives.

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

Deploy Server

Other Tools