telegram-mcp

Overview Schema Source Related Servers Discussions Admin

tg_create_group

Create a Telegram supergroup or channel, and optionally invite users right away using their IDs, usernames, or exact titles.

Instructions

Create a supergroup or a channel and optionally invite people right away.

Args: title: name of the new chat. users: who to invite (ids, @usernames or exact titles). kind: "group" (supergroup) or "channel" (broadcast). about: description.

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": {
      "title": "<title>"
    },
    "name": "tg_create_group"
  }
}

Input Schema

Name	Required	Default
`kind`	No	group
`about`	No
`title`	Yes
`users`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 17, 2026

TDQS

A4.3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the key behavior of creating a supergroup/channel and optionally inviting users, and clarifies 'kind' values. Yet it does not mention permissions, reversibility, or other side effects, missing important context for a mutation tool.

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 concise and well-structured, with a one-sentence purpose followed by a clean Args list. No wasted words, and every sentence contributes meaningful information.

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?

The description is adequate for invoking the tool: required title, optional users, and kind/about are all addressed. Since an output schema exists, return values need no explanation. The only gap is lack of explicit guidance on when not to use this tool, which is minor given the clear purpose.

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

Parameters5/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 compensate. It fully does: each parameter is explained with added meaning—title as name, users with accepted formats, kind with values, and about as description. This goes well beyond the schema's bare types and defaults.

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?

The description clearly states the action 'Create a supergroup or a channel' and optionally inviting people, using a specific verb and resource. It distinguishes itself from sibling tools like tg_chat_edit and tg_invite by focusing on creation.

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?

The description gives clear context: use this to create a new chat and optionally add users immediately. However, it does not explicitly mention alternatives like tg_invite for existing chats or tg_chat_edit for modifications, so there are no exclusions or when-not-to-use guidance.

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

Deploy Server