Fast MCP Telegram

by ru.l1979.tg-mcp

Find chats

find_chats

Read-onlyIdempotent

Find users/groups/channels by name, username, or phone. Comma-separated usernames are searched in parallel and results are merged round-robin. Global search (query required) searches all Telegram; with min_date, max_date, or filter, search uses dialog list or a named filter; include_peers filters use last-activity from GetPeerDialogs; flag-based filters use dialog list dates. Success: dict with key chats (list of chat objects). Full documentation: https://github.com/alexeyleshchenko/fast-mcp-telegram/blob/main/docs/Tools-Reference.md

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum chats to return (recommended 50 or less).
`query`	No	Name, username (no @), phone (+country…), or comma-separated usernames for batch lookup. Example: 'alice,bob,charlie'. Required for global search unless you use min_date/max_date or folder alone.
`folder`	No	Telegram folder name (case-insensitive exact match after normalization). In Telegram's UI these are called folders; internally they are "dialog filters" — saved filter presets that group chats by custom criteria (pinned, unread, business, etc.). See Filters-vs-Folders.md for the technical distinction.
`public`	No	If true, prefer chats with a public username; if false, without. Does not apply to private DMs. Omit to skip this filter.
`max_date`	No	Inclusive maximum date filter (ISO 8601 date or datetime). Omit for no upper bound.
`min_date`	No	Inclusive minimum date filter (ISO 8601 date or datetime). Omit for no lower bound.
`chat_type`	No	Comma-separated chat kinds: private, bot, group, channel. Case-insensitive; extra spaces allowed.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`code`	No
`chats`	No
`error`	No
`action`	No
`params`	No
`exception`	No
`operation`	No
`error_code`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedJun 26, 2026

changedInput schema / properties / query / description

Previous value: -"Name, username (no @), phone (+country…), or comma-separated multi-queries. Required for global search unless you use min_date/max_date or folder alone."New value: +"Name, username (no @), phone (+country…), or comma-separated usernames for batch lookup. Example: 'alice,bob,charlie'. Required for global search unless you use min_date/max_date or folder alone."

First observedJun 18, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The description discloses useful behavioral details like parallel comma-separated search, round-robin merging, and mode switching based on parameters, adding value beyond the readOnly/idempotent annotations. However, it references parameters (include_peers, flag-based) that do not exist in the input schema, which undermines transparency and adds confusion.

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 moderately concise with a clear front-loaded purpose, but includes technical jargon (GetPeerDialogs, flag-based filters) and references to undocumented parameters, making it less clear than it could be. Every sentence has some content, but some could be streamlined or clarified.

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?

The tool is complex with multiple search modes, and the description references parameters not present in the schema, creating ambiguity about how to properly invoke the tool. The output schema exists and the return format is mentioned, but the mismatch between description and schema leaves significant gaps in understanding.

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?

The input schema documents all 7 parameters with descriptions, so baseline is 3. The description adds some context about batch lookup and search modes, but does not compensate for the phantom parameters mentioned. It adds marginal value beyond the schema's already-good parameter descriptions.

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 clearly states the tool finds users/groups/channels by name, username, or phone, which is specific and distinguishes it from message-searching siblings. The verb 'Find' and resource 'users/groups/channels' are unambiguous.

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 provides conditional behavior for different search modes (global vs dialog list) but does not explicitly state when to prefer this tool over alternatives like search_messages_globally. It implies usage scenarios but lacks explicit exclusions or alternative recommendations.

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

All Fast MCP Telegram tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?