Skip to main content
Glama
telegram-channels-mcp

telegram-channels-mcp

list_chats

Read-only

Lists your Telegram channels, groups, and private chats in recent-first order, with filters for chat type, result limit, and admin-owned or administered channels and groups.

Instructions

List the user's Telegram dialogs: channels, groups and private chats, most recent first. Use admin_only=true to get only channels and groups the user owns or administers

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_chats"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoall
limitNo
admin_onlyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by stating the result ordering (most recent first) and the admin_only narrowing behavior. It does not disclose pagination behavior or the implicit 100-dialog default cap, which matter for an open-world listing tool.

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

Conciseness4/5

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

Two tight sentences with no filler; the core purpose and ordering are front-loaded before the admin_only variant. The second sentence is parameter guidance rather than routing guidance, but it still earns its place.

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?

An output schema exists, so return-value explanation is not required. For a three-parameter listing tool the definition is serviceable but leaves the `limit` semantics and any pagination/truncation behavior unaddressed, which an agent needs in order to enumerate fully.

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 description coverage is 0%, so the description must carry parameter meaning. It does well on admin_only, clarifying it returns only channels and groups the user owns or administers, but says nothing about `kind` (whose enum is self-explanatory) or `limit` (default 100, unclear if it is a hard cap or page size). Partial compensation for the coverage gap.

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?

"List the user's Telegram dialogs: channels, groups and private chats, most recent first" gives a specific verb, resource, scope, and ordering. It is clearly distinguishable from siblings like search_messages or read_messages, though it never explicitly contrasts with them.

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 explains one usage path (admin_only=true narrows to owned/administered channels and groups), which is genuine when-to-use guidance for a parameter. It offers no guidance on when to prefer search_messages or read_messages over enumerating dialogs, and no exclusions.

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