telegram-mcp

by jgalea

Overview Schema Source Related Servers Discussions Admin

Python

Local

create_channel

Creates a new Telegram channel with an optional description, enabling direct message broadcasting to subscribers.

Instructions

Create a new channel

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": "create_channel"
  }
}

Input Schema

Name	Required	Description	Default
`about`	No
`title`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Aug 30, 2026

TDQS

C2.4/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 disclose behavioral this description does not mention permissions, side effects, idempotency, uniqueness constraints, or what happens after creation. The behavior is underspecified beyond the basic action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, with no wasted words. However, this is under-specification rather than efficient completeness: it is concise but at the expense of the additional context an agent needs.

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 creation tool with no annotations and no output schema, the description is too thin. It does not clarify what a channel is, what fields matter, what the result of creation looks like, or how this tool fits among siblings like create_group.

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

Parameters1/5

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

Schema description coverage is 0% and the description adds no meaning to the title or about parameters. The required title field is not explained, and about is entirely omitted, so the agent has no additional semantic signal beyond the parameter names.

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 names a specific verb and resource—'Create a new channel'—so an agent can tell it apart from unrelated tools like search_messages or delete_chat. However, it does not explain how a channel differs from the closely related create_group sibling, so differentiation is not fully fleshed out.

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?

No guidance is given about when to use create_channel versus create_group or set_chat_title. There are no prerequisites, exclusions, or alternative tool references, leaving the agent to guess the intended context.

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