Skip to main content
Glama
starnikovoleg

channelindex-mcp

Search public Telegram channels

telegram_search_channels
Read-only

Search Telegram's global index to locate public channels and groups by title or handle. Use short topical keywords to seed a topic and discover relevant channels.

Instructions

Telegram's own global search over public channels and groups, by title and handle. Good for seeding a topic; telegram_similar_channels is what expands a seed into a neighbourhood. Short topical words work better than sentences.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesKeyword to search for.
formatNoOutput shape. "markdown" is compact prose for a model to read; "json" is the raw API response. Default "markdown".

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.1

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already establish read-only and open-world behavior. The description adds useful behavioral context: the search is Telegram's own, restricted to title and handle, and that short keywords are more effective—an important nuance for the agent's query strategy.

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?

Three sentences, all load-bearing: what it searches, when to use it versus the sibling, and a practical tip. No repetition of the title or schema, and the core distinction is front-loaded.

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?

For a simple read-only search tool with fully documented parameters, this description provides enough to call it correctly: scope, matching criteria, use case, and sibling alternative. The format parameter already covers output shape, so no additional return-value explanation is needed.

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. The description goes beyond the schema by explaining that query semantics favor short topical words and that results are matched by title and handle, which meaningfully informs how the agent should set the query parameter.

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 clearly identifies the tool as Telegram's global search over public channels and groups, by title and handle. It explicitly distinguishes itself from telegram_similar_channels, which is the expansion step, so an agent can select the right starting point.

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?

It states this tool is good for seeding a topic and names telegram_similar_channels as the alternative for expanding a seed into a neighbourhood. It also provides practical guidance that short topical words outperform sentences.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/starnikovoleg/channelindex-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server