Telegram MCP — Next Generation

List All Telegram Chats and Channels

list_chats

Read-onlyIdempotent

List all accessible Telegram chats, groups, channels, and direct dialogs with pagination and filters by type, unread status, or archived state to locate specific conversations.

Instructions

List all accessible chats, groups, channels, and direct dialogs with pagination support. Use when locating specific conversations by title or type. For a quick recent dialogs overview, use get_chats.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of items or records to retrieve (integer between 1 and 100).
`account`	No	Optional account label for multi-account environments. If omitted in single-mode, the default account is used. In multi-mode without an account, read-only tools fan out across all configured accounts.
`archived`	No	If true, queries archived chats instead of main inbox chats.
`chat_type`	No	Filter chats by type: 'all', 'private', 'group', 'channel', or 'bot'.
`with_about`	No	If true, includes the about/bio description in the retrieved chat details.
`unread_only`	No	If true, filters and returns only chats with unread messages.
`unmuted_only`	No	If true, filters and returns only chats whose notifications are active.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.1.1Sep 11, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description only adds that pagination is supported, without explaining the mechanism (there is no offset/cursor parameter, only limit), so the added behavioral value is modest.

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?

Three short sentences, zero filler, and the capability statement is front-loaded before the routing guidance. Every sentence earns its place.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. The one remaining gap is that 'pagination support' is asserted but not operationalized, leaving an agent unsure how to page through results beyond the limit parameter.

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 100% and all seven parameters are documented in the schema, so the baseline of 3 applies. The description alludes to filtering by title or type but adds no semantics beyond what the schema fields (chat_type, archived, unread_only, etc.) already state.

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 gives a specific verb (List) plus the resource and its full scope (chats, groups, channels, direct dialogs) and adds the pagination trait. It explicitly distinguishes itself from the sibling get_chats, so an agent can separate the two without opening either schema.

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?

It clearly states when to reach for this tool ('locating specific conversations by title or type') and names the alternative for the other case ('quick recent dialogs overview, use get_chats'). It does not, however, distinguish itself from neighboring search tools such as search_public_chats or search_contacts, which also target conversation discovery.

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