Skip to main content
Glama
overpod

MCP Telegram

telegram-search-global

Read-only

Query all public Telegram chats and channels to find messages by text, with optional date range and result limit.

Instructions

Search messages globally across all public Telegram chats and channels

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results
queryYesSearch text
maxDateNoUnix timestamp: only messages before this date
minDateNoUnix timestamp: only messages after this date
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds value by specifying the scope 'across all public Telegram chats and channels', clarifying that it does not access private chats. This provides useful behavioral context beyond the annotations.

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?

The description is a single sentence that directly communicates the tool's purpose with no unnecessary words. It is well-structured and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the core functionality but does not mention the return format or pagination behavior. Given that there is no output schema, the agent may need more context about what results look like. It is adequate but not fully comprehensive.

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

Parameters3/5

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

Schema coverage is 100%, so the description does not need to add much. It provides no additional parameter explanation beyond the schema's own descriptions. Baseline of 3 is appropriate.

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 states the verb 'Search', the resource 'messages', and the scope 'globally across all public Telegram chats and channels'. It effectively distinguishes this tool from siblings like 'telegram-search-messages' which likely operate within a specific chat context.

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

Usage Guidelines3/5

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

The description implies that this tool is for global public search, but it does not explicitly state when to use it versus alternatives like 'telegram-search-messages' or other search-related tools. Instructions on prerequisites or exclusions are missing.

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

Install Server

Other Tools

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/overpod/mcp-telegram'

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