Skip to main content
Glama
Sign In
telegram-bot-mcp

telegram-bot-mcp

by FantomaSkaRus1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

restrict_chat_member

Restrict a user's permissions in a Telegram chat by providing user ID and a permissions JSON object. Optionally target a specific chat or set an expiration time.

Instructions

Restrict a user's permissions in a chat. If chat_id is omitted, targets the default log group.

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": {
      "user_id": "<user_id>",
      "permissions": "<permissions>"
    },
    "name": "restrict_chat_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idNoChat ID or @channel_username. Optional — defaults to log group
user_idYesUser ID to restrict
until_dateNoUnix timestamp when restrictions will be lifted
permissionsYesJSON string with ChatPermissions object
use_independent_chat_permissionsNoUse independent permissions for each privilege instead of implicit grouping

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.3

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It implies mutation ('restrict') but does not disclose reversibility, overrides, required permissions, or any side effects. Minimal beyond default chat_id behavior.

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 main action. Second sentence adds key default behavior. No redundancy.

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?

Missing output schema, no annotation coverage. Description does not explain return value, error conditions, or parameter details like permissions JSON format. Incomplete for a tool with 5 parameters and moderate complexity.

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 covers all 5 parameters with descriptions. Description adds no extra meaning (e.g., format of permissions JSON or when to use use_independent_chat_permissions). Baseline 3 with no additional value.

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?

Clearly states the verb 'restrict' and resource 'user's permissions in a chat'. Distinguishes from sibling tools like 'ban_chat_member' (permanent ban vs temporary restriction) and 'set_chat_permissions' (global chat settings).

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

Usage Guidelines2/5

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

Only mentions defaulting to the log group when chat_id is omitted. Lacks guidance on when to use this tool vs siblings (e.g., ban vs restrict), prerequisites (admin rights), or conditions to avoid.

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