Skip to main content
Glama
Telegram Live MCP

Telegram Live MCP

by sugestr

list_folders

Read-only

List Telegram folders and their chats, or retrieve chats in a specific folder by name or ID to understand how conversations are organized.

Instructions

Папки Telegram этого аккаунта и их состав. Без folder — список папок: id, название, сколько чатов, явно добавленные и набранные правилами типов (группы, каналы, контакты…). С folder (название или id из списка) — чаты одной папки: id, название, вид. Папка говорит, к чему относится чат. Состав считается как у коллектора: «только непрочитанные» и «без заглушённых» — свойства отображения, на состав они не влияют.

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_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoсколько чатов папки вернуть, до 1000; по умолчанию 300
folderNoназвание папки (регистр не важен) или её id; без него — список папок
refreshNoпересобрать список диалогов перед подсчётом

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: how membership is computed, that 'only unread' and 'without muted' are display properties that do not change composition, and what each mode returns. It does not discuss cost or freshness beyond the refresh parameter.

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?

The two modes are front-loaded and separated by clear signals ('Без folder' / 'С folder'), which makes it easy to scan. The closing sentence on collector counting semantics is slightly tangential but earns its place by preventing a wrong inference about filtering.

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?

With no output schema, the description compensates by enumerating returned fields for both modes, and it explains the counting rules an agent would otherwise guess at. Only the refresh behavior and pagination at the 1000 limit are left to the schema, which is acceptable for a read-only list tool.

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%, so the schema already documents limit, folder and refresh. The description restates folder's dual role (name case-insensitive or id from the list) and clarifies that limit bounds chats of a folder, but adds no format or edge-case detail beyond the schema. Baseline 3 applies.

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 names the concrete resource (Telegram account folders and their chat composition) and explicitly splits the tool into two behaviors: folder list when no folder is given, chat list for one folder when it is. The return fields for each mode are named, so an agent knows exactly what it gets without opening the 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 states clearly when to call with folder (name or id from the list) versus without it, which is the main selection decision for this tool. It gives no guidance against siblings such as find_dialogs or search_chat, so the routing to alternatives is left implicit.

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