Skip to main content
Glama
telegram-keyword-search

telegram-keyword-search

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APIFY_TOKENNoOptional. 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_telegram_channelsA

Search public Telegram channels that you name for a keyword. Free, no API key, no Telegram account.

Uses Telegram's own in-channel search on the public web preview (t.me/s/<channel>) and
keeps only posts that contain the keyword as written or as a #hashtag. Returns at most
the 20 newest search results per channel, up to 10 channels. It does NOT find channels
for you; use start_keyword_search when you don't know which channels talk about the keyword,
or need more posts, dates or only new posts.

Args:
    keyword: word or phrase, e.g. "end-to-end encryption" or "Solana".
    channels: public channel usernames or links, e.g. ["durov", "@telegram", "t.me/s/cointelegraph"].
    include_all: keep every post Telegram's search returns, not only exact matches.

Returns {"posts": [...], "channels": [{"channel", "status", "returned", "kept"}]}.
status "notFound" means no public channel with that name or its web preview is off.
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.

Starts the hosted Apify Actor "datalume/telegram-keyword-search-scraper" with your own
Apify account. Requires the APIFY_TOKEN environment variable. It is PAID: per matching
post plus a small fee per keyword when channels are found (current price:
https://apify.com/datalume/telegram-keyword-search-scraper ); non-matching posts and
unreadable channels are not charged. Starting a search spends money even if the results
are never fetched, so start one only when the user wants the posts. The run stops at
max_posts_per_keyword and at max_total_charge_usd. A run takes from a few seconds to
about two minutes (15 Nov 2026: 3 keywords, 259 posts from 19 channels in 2 min 15 s).

Args:
    keywords: words or phrases, e.g. ["Hyperliquid"]. Each keyword is searched separately.
    channels: optional channels that are always searched, e.g. ["durov"].
    discover_channels: find channels for each keyword with Google (site:t.me). Set false to search only `channels`.
    max_channels_per_keyword: found channels searched per keyword, 1-50.
    match_mode: "phrase" (exact phrase or #hashtag), "allWords" or "telegram" (everything Telegram returns).
    max_posts_per_keyword: stop a keyword after this many matching posts. Keep small to control cost.
    date_from: only posts since a date ("2026-11-01") or a period ("7 days", "24 hours"). Empty = any date.
    only_new_posts: return only posts published since the previous run of the same keyword in each channel.
    max_total_charge_usd: hard spending cap for this search, in USD.
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.

Waits up to wait_secs for the search to finish. Returns {"finished", "status", "posts",
"message"}. If "finished" is false the search is still running and "posts" is empty:
call get_keyword_results again with the same run_id (do not start a new search).

Args:
    run_id: the run_id returned by start_keyword_search.
    wait_secs: how long to wait for the search to finish, 0-45 seconds.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.7/5.0

Scored across 3 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues