telegram-keyword-search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | No | Optional. Apify API token, only needed for start_keyword_search and get_keyword_results. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_telegram_channelsA | Search public Telegram channels that you name for a keyword. Free, no API key, no Telegram account. |
| start_keyword_searchA | Start a Telegram keyword search that also FINDS the channels talking about each keyword, and return a run_id immediately. Step 1 of 2: then call get_keyword_results(run_id) to get the posts. |
| get_keyword_resultsA | Get the posts found by a search started with start_keyword_search. Step 2 of 2. Reading results is free; it never starts a new search. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The two search tools overlap in domain (both search Telegram by keyword), but the descriptions clearly separate the free named-channel search from the paid channel-discovering search. get_keyword_results is clearly a retrieval step and cannot be confused with either search tool.
All three tools use snake_case with a verb-first pattern: search_telegram_channels, start_keyword_search, get_keyword_results. The start/get pair also signals a coherent two-step workflow.
Three tools are well-scoped for a narrow keyword-search server: a direct search, an asynchronous discovery search, and a results fetcher. The async split is justified by the long-running paid operation.
The surface covers both the free direct-search workflow and the paid discovery-then-retrieval lifecycle. Minor gaps exist around run management (e.g., cancel or list runs) and channel inspection, but core keyword-search tasks are covered.