Skip to main content
Glama
Sign In
Telegram MCP

Telegram MCP

by Anonymouse8882
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_dialogs

Retrieve recent Telegram chats with filters for type, unread, archived, and name query.

Instructions

列出最近的对话（聊天列表）。

Args: limit: 返回条数上限，最多 500。 archived: True 则读取归档文件夹。 kind: 只保留某一类对话。 unread_only: 只返回有未读消息的对话。 query: 按对话名字过滤（不区分大小写）。

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

Input Schema

NameRequiredDescriptionDefault
kindNoall
limitNo
queryNo
archivedNo
unread_onlyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 behavior. It does not mention sorting order, pagination, caching, permissions, or how filters interact. The parameter explanations are minimal.

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 very concise: one line for purpose, then a bullet-like list of parameters. No redundant text, front-loaded with the main action.

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?

With an output schema present, the description need not detail return structure. However, it omits ordering, default parameter interactions, and usage context relative to sibling tools. Adequate for a simple list tool but with gaps.

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

Parameters4/5

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

Schema coverage is 0%, but the description provides Chinese explanations for all 5 parameters, clarifying limit (max 500), archived (archive folder), kind (dialog type), unread_only, and query (case-insensitive name filter). This adds meaning beyond schema property 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 clearly states '列出最近的对话（聊天列表）' (list recent dialogs/chat list), which identifies the verb and resource. It distinguishes from sibling list tools like list_contacts by specifying 'dialogs' rather than contacts.

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 on when to use this tool versus alternatives such as search_messages or get_chat_info. No conditions or exclusions are mentioned.

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

Deploy Server

Other Tools