Skip to main content
Glama
telegram-channels-mcp

telegram-channels-mcp

search_messages

Read-only

Search messages within a specific Telegram channel or chat by full-text query, returning newest matches first with optional result limits.

Instructions

Full-text search inside one channel or chat using Telegram's own search, newest matches 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": {
      "chat": "<chat>",
      "query": "<query>"
    },
    "name": "search_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes
limitNo
queryYes
max_charsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint, so safety is covered. The description adds genuinely new behavioral context: search is delegated to 'Telegram's own search' (server-side matching semantics, not local substring filtering) and results come back newest-first. Pagination and rate-limit behavior remain undisclosed.

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?

A single front-loaded sentence with no filler, and the scoping and ordering facts arrive immediately. It is efficient but arguably too terse given the undocumented parameters.

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?

An output schema exists, so return values need no explanation, and the annotations cover safety. However, for a four-parameter tool with zero schema descriptions, the definition leaves the agent without enough information to set 'limit' or 'max_chars' confidently, and offers no routing guidance against siblings.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden for four parameters. It only implies what 'chat' and 'query' mean; 'limit' and especially 'max_chars' (likely truncation of message text) get no explanation anywhere, leaving half the parameters opaque.

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?

States a specific verb and resource ('Full-text search ... messages'), a precise scope ('inside one channel or chat'), and result ordering ('newest matches first'). This clearly distinguishes it from read_messages, which would retrieve rather than search.

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?

Usage is only implied: the phrase 'inside one channel or chat' tells the agent the search is scoped to a single chat, so it should be used after a chat is known. There is no explicit guidance on when to prefer this over read_messages or get_comments, and no stated prerequisites.

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