Skip to main content
Glama
Sign In
telegram-mcp-connector

telegram-mcp-connector

by nitatsuu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Search Messages

search_messages
Read-only

Search Telegram messages by full-text query to find chats or specific messages, returning newest results first and optionally limiting the search to one chat.

Instructions

Full-text search (Telegram server-side search), newest first.

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": {
      "query": "<query>"
    },
    "name": "search_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatNoLimit to one chat; omit to search all chats
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety context is covered. The description adds useful behavioral context by noting server-side search and newest-first result ordering, but it does not mention rate limits, pagination, or other operational details.

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

Conciseness4/5

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

The description is a single front-loaded sentence with no wasted wording. It is perhaps too terse for the tool's complexity, but structurally it is clear and efficient.

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 presence of an output schema and annotations reduces the burden on the description. However, given three parameters with only 33% schema description coverage, the definition is minimally adequate but does not fully explain usage, parameter semantics, or search scope.

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 low at 33%, so the description should compensate more than it does. It adds meaning to the query parameter via 'full-text search' and implies ordering, but it does not explain the chat filter or limit behavior beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: full-text search of messages, with Telegram server-side search and newest-first ordering. It is clear what the tool does, but it does not explicitly differentiate itself from siblings like get_messages or get_message_context.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus get_messages, list_chats, or other siblings. The description implies search usage but gives no exclusions, prerequisites, or alternative-selection guidance.

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

Deploy Server

Other Tools