Skip to main content
Glama
theYahia

@theyahia/tgstat-mcp

by theYahia

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TGSTAT_TOKENYesAPI-ключ TGStat.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_channelsB

Search Telegram channels by query, with optional category / language / country / type filters. Returns curated channel cards.

get_channelA

Get a Telegram channel's profile: subscribers, category, citation index (ci_index), RKN verification. For reach/ERR use get_channel_stats.

get_channel_statsA

Get a channel's statistics: average post reach, ERR%, daily reach, citation index.

get_channel_mentionsC

Find where a channel is mentioned or forwarded by other channels and chats.

compare_channelsA

Compare several channels side by side on subscribers, average reach and ERR (one channels/stat lookup per channel).

get_channel_postsA

Get recent posts of a channel with view metrics. Supports an optional date range and pagination.

get_postA

Get details of a single post: views, forwards, reactions, text.

search_postsB

Full-text search across Telegram posts, with optional source-type / category / language / country / date filters.

get_post_statsA

Get a post's engagement dynamics: views, forwards and reactions over time.

get_channel_subscribersB

Subscriber-count history of a channel over time.

get_channel_viewsC

Total post-views history of a channel over time.

get_channel_avg_reachB

Average post-reach history of a channel over time.

get_channel_errB

ERR (engagement rate by reach) history of a channel over time.

get_channel_forwardsC

Posts from other channels that forwarded this channel's content.

get_word_mentionsA

Track how often a keyword is mentioned across Telegram over time (mentions + views per period).

get_word_mentions_by_channelsB

Break down keyword mentions by the channels that mention it most (channel + mention/view counts).

list_categoriesA

List available channel category codes (use as the category filter in search).

list_countriesA

List available country codes (use as the country filter in search).

list_languagesA

List available language codes (use as the language filter in search).

get_usageA

Show your TGStat API usage and quota: requests / channels / words spent vs allowed, and package expiry.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 20 tools

Disambiguation4/5

Most tools target a distinct resource and metric, such as current channel profile, historical subscribers, views, reach, or ERR. However, get_channel_mentions and get_channel_forwards both cover forwarding behavior, and get_channel_stats overlaps somewhat with the individual metric history tools.

Naming Consistency5/5

Tool names follow a clear and predictable pattern: get_<resource>_<detail>, search_<resource>, list_<enum>, and compare_channels. Resources are consistently singular or plural as appropriate, and all verbs are consistent and readable.

Tool Count4/5

Twenty tools is on the heavier side but still justified for a Telegram analytics server that covers channels, posts, keyword mentions, reference lists, and usage. The count is slightly high but not bloated; each tool serves a distinct analytics need.

Completeness5/5

The server covers the core TGStat analytics workflows: channel search and profiles, current and historical stats, post search and details, post engagement, keyword mentions, reference data, and quota usage. For a read-only analytics API, the surface is comprehensive and leaves no critical dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues