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

telegram-bot-mcp

by FantomaSkaRus1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

set_chat_administrator_custom_title

Assign a custom title up to 16 characters to an admin in a chat or the default log group.

Instructions

Set a custom title for an admin 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>",
      "custom_title": "<custom_title>"
    },
    "name": "set_chat_administrator_custom_title"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idNoChat ID or @channel_username. Optional — defaults to log group
user_idYesUser ID of the admin
custom_titleYesCustom title (up to 16 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.3

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states the action and default behavior, but lacks information on prerequisites (e.g., user must already be an admin), required permissions, side effects (e.g., overwrites existing title), or limitations (e.g., works only in supergroups/channels).

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?

The description is two sentences with no extraneous information. The first sentence states the core purpose, and the second provides key optional behavior. It is concise and front-loaded.

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

Completeness3/5

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

Given the lack of annotations and output schema, the description is adequate but not fully complete. It omits important context such as permissions needed and the requirement that the user must already be an administrator. The sibling list and schema help, but the description itself could be richer.

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%, with each parameter described in the schema. The description adds only a restatement of the chat_id default behavior already present in the schema. Thus it does not significantly enhance parameter understanding beyond what the schema provides, meeting the baseline.

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 clearly states the action ('Set a custom title for an admin in a chat') with a specific verb and resource. It distinguishes from sibling tools like promote_chat_member and ban_chat_member by focusing on setting a custom title, though it could be more explicit that this only applies to administrators to differentiate it from set_chat_member_tag.

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?

The description provides context for the optional parameter (chat_id defaults to log group) but does not explain when to use this tool versus siblings like promote_chat_member or set_chat_member_tag. No explicit when-not or alternative guidance is given.

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