Limzo – Telegram Group Stats

List or search public Telegram groups

list_groups

Read-only

Call this to discover Telegram groups tracked by Limzo — to browse the directory, filter by language, or find a group's slug for get_group_stats. Optional query filters case-insensitively over group title, username, slug, and description. Optional lang (ISO 639-1, e.g. "fa", "es") keeps only groups where that language is a meaningful share of what members write — the way to answer "find active Persian/Spanish groups". Omit both to list the top groups by Limzo Score. The directory covers PUBLIC groups only — a group with no t.me handle is never listed, though it may still have a /s/ page. Each row carries a language mix (primary language + top languages as percentages); rows also include slug, title, username, plan, member_count, 7-day messages and active members, score and page URLs, plus total_matches so you can tell when more groups matched than were returned.

Input Schema

TableJSON Schema

Name	Required	Description
`lang`	No	ISO 639-1 language code (e.g. "fa", "es", "en"). Keeps only groups where that language is a meaningful share of the group.
`limit`	No	Maximum groups to return. Defaults to 20, capped at 50.
`query`	No	Keyword matched case-insensitively against group title, username, slug, and description. Omit to list the top groups by Limzo Score.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`docs`	No	Human-readable API documentation.
`lang`	No	The applied ISO 639-1 language filter, or null when not filtering by language.
`query`	No	The normalized search keyword, or null when listing top groups.
`groups`	Yes
`openapi`	No	Machine-readable OpenAPI document for the REST API.
`total_matches`	Yes	Groups that matched, before the limit was applied.

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, so the description's job was to add context, and it does: the PUBLIC-groups-only coverage rule, the Limzo Score ranking when all filters are omitted, and the total_matches signal for truncated results. The 'meaningful share of what members write' qualifier for the lang filter is behavioral nuance the structured data cannot convey. Nothing contradicts the annotations.

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 description is dense but every clause earns its place -- purpose, param semantics, default behavior, coverage limitation, row contents, and truncation flag. It is front-loaded with the purpose and has no filler, though it sits near the upper bound of comfortable length for a 3-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that an output schema covers return values and annotations cover the read-only safety profile, the description supplies everything else an agent needs: when to call it, param semantics, defaults, and behavioral caveats like public-only coverage and total_matches. The only omission -- an explicit word about get_global_stats -- does not undermine correct invocation.

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 100%, so the baseline is 3, but the description still adds real meaning: query 'filters case-insensitively over group title, username, slug, and description', lang is pinned to ISO 639-1 with a meaningful-share semantic and an example, and the omit-both default is spelled out. It enriches both filters rather than merely restating the schema.

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 states a specific verb and resource -- 'discover Telegram groups tracked by Limzo' -- and names its immediate use case of resolving a slug for get_group_stats, so an agent can place it in the workflow. It is clearly distinct from the sibling stats tools.

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?

The description gives explicit contexts for calling it: browsing the directory, filtering by language, or finding a slug for get_group_stats, and even maps a natural-language request ('find active Persian/Spanish groups') to the lang parameter. It does not explicitly contrast itself with get_global_stats or state when to avoid it, so exclusions are left to inference.

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

All Limzo – Telegram Group Stats 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.

TDQS

A4.6/5.0

Disambiguation4/5

get_group_stats and list_groups are clearly distinct, but get_global_stats and list_groups both surface top groups by Limzo Score, so an agent could pick the wrong one for a 'top groups' request. The descriptions help disambiguate, but the overlap keeps this from being a perfect score.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: get_global_stats, get_group_stats, list_groups. The verbs get and list are appropriate for their actions, and the scope is clear in each name.

Tool Count5/5

Three tools is at the low end but well-scoped for a read-only stats server: one for network-wide stats, one for a single group's stats, and one for directory discovery. Each tool earns its place with no redundancy.

Completeness4/5

The core surface is covered: global stats, per-group stats, and group discovery/search. The only notable gap is that list_groups exposes total_matches but no pagination parameter, so large result sets may be truncated without a way to page through them.

Resources

Need Help?