Skip to main content
Glama
Hermoso

Hermoso

Official

Find Telegram chat ids

list_telegram_chats
Read-onlyIdempotent

Find the chat IDs a Telegram bot can be addressed by scanning updates from the last 24 hours; a webhook returns an empty list, so absence is not proof of no access.

Instructions

Find the chat ids this Telegram bot can be addressed by. STATE THE LIMIT WHENEVER YOU USE IT: this is NOT the list of chats the bot belongs to — the Bot API publishes no such method — it is every chat that SENT the bot an update in the last 24 hours, which is as long as Telegram keeps an update. A channel the bot posts to every day but nobody messages will NOT appear here, and its absence means nothing at all: post to it by @username or numeric id anyway. If the bot has an outgoing WEBHOOK configured the list is empty for that reason alone (Telegram: getUpdates "will not work if an outgoing webhook is set up"), and the reply says so rather than reading as an empty account. Nothing is consumed — no update offset is confirmed, so this cannot eat the bot’s pending updates. Free, 0 credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_telegram_chats"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNohow many recent updates to scan, 1–100 (default 100)
accountNowhich connected account: its @handle or id from list_connector_accounts; needed only when several are connected

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.465
    • addedInput schema / properties / account
      Added value: +{
      +  "description": "which connected account: its @handle or id from list_connector_accounts; needed only when several are connected",
      +  "type": "string"
      +}
  2. Addedv0.1.161

TDQS

A4.1/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: the list covers only chats that sent an update in the last 24 hours, is empty when an outgoing webhook is configured, and does not consume pending updates by confirming an offset. It also notes the zero-credit cost. This is unusually rich disclosure for a read-only tool.

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 front-loaded and each sentence addresses a real failure mode, especially the 24-hour window and webhook caveat. It is somewhat emphatic and repetitive in places, but not wasteful enough to drop below 4.

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

Completeness4/5

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

Given no output schema, the description explains the critical edge cases that produce an empty or misleading result and tells the agent not to treat absence as definitive. It could say more about the exact shape of returned chat entries, but the operational completeness is strong.

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%, and both parameters (limit, account) are fully described in the schema. The description adds no parameter-specific syntax or meaning beyond that baseline, so a 3 is appropriate.

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?

States a specific verb and resource: find the chat ids this Telegram bot can be addressed by. It explicitly corrects the likely misconception that this lists all chats the bot belongs to, but it does not directly contrast with sibling tools such as post_to_telegram.

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

Usage Guidelines4/5

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

Gives clear operational guidance: absence from this list does not mean the bot cannot post, and posting should be done by @username or numeric id anyway. It also explains the webhook case that makes the list empty, but it does not explicitly state when to call this versus post_to_telegram.

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