Skip to main content
Glama
telegram-keyword-search

telegram-keyword-search

search_telegram_channels

Search named public Telegram channels for a keyword and get matching posts with links, dates, and views. Use it when you already know which channels to check.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword": "<keyword>",
      "channels": "<channels>"
    },
    "name": "search_telegram_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYes
channelsYes
include_allNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does most of it: it names the underlying mechanism (Telegram's public web preview at t.me/s/<channel>), the filtering rule (exact keyword or #hashtag), hard caps (20 newest per channel, 10 channels), the no-auth/no-cost profile, and the meaning of status "notFound". It stops short of rate-limit or partial-failure behavior, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the one-line purpose, then the mechanism/limits, then the alternative, then an Args block. Every sentence contributes either a constraint, a routing decision, or parameter semantics; nothing is repeated from the structured fields.

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?

There is no output schema, and the description compensates by sketching the return shape ("posts" array plus per-channel status/returned/kept) and explaining the one non-obvious status value. For a 3-parameter read-only search, an agent has everything needed to call it and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must define all three parameters, and it does: keyword with example phrases, channels with the three accepted formats ("durov", "@telegram", "t.me/s/cointelegraph"), and include_all explained as "keep every post Telegram's search returns, not only exact matches". This adds real meaning the bare schema does not convey.

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?

"Search public Telegram channels that you name for a keyword" gives a specific verb, resource, and a scope constraint that separates it from a channel-discovery tool. It also states the negative case ("It does NOT find channels for you") and names the sibling that handles it, so the boundary is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use this when you already know the channels, use start_keyword_search when you don't know the channels, need more posts, need dates, or only want new posts. It also establishes the precondition that channel names must be supplied by the caller.

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