Skip to main content
Glama
GeiserX

telegram-archive-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

list_chats

Read-only

List archived Telegram chats, most recent first. Get the chat_id needed by other tools and paginate with offset while has_more is true.

Instructions

List archived Telegram chats, most recent first. Use this first: each chat's ref is the chat_id the other tools take. Each row also carries id (the numeric Telegram chat id), type, accounts (the archive account ids holding the chat), and its title or name. The answer is {chats, total, limit, offset, has_more}; page with offset while has_more is true.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum chats to return (default 100, max 500)
offsetNoNumber of chats to skip (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum chats to return (default 100)"New value: +"Maximum chats to return (default 100, max 500)"
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Number of chats to skip (default 0)",
+  "type": "number"
+}
  2. Addedv0.1.3

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint, so the description carries the rest of the burden and does so well: it discloses ordering, the cross-tool contract (ref = chat_id), the fields on each row (id, type, accounts, title/name), and the exact response envelope plus the has_more-driven paging contract. With no output schema present, this is exactly the behavioral context an agent needs.

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 tightly packed sentences with no filler, front-loaded with purpose and the 'use this first' directive before the field list and the paging contract. Every clause carries information an agent would otherwise have to infer.

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 two-parameter, no-required-argument, read-only list tool with no output schema, the description supplies the return shape, the field meanings, the ordering guarantee, and the pagination termination rule. Nothing needed to call it correctly is missing.

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% and both limit and offset are documented there, so the 3 baseline applies; the description adds value by tying offset to the has_more flag in the response envelope, giving the parameter an operational meaning the schema alone lacks. It does not restate or extend the limit/default/max semantics.

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 ('List archived Telegram chats') plus the ordering ('most recent first'), and further positions itself against the sibling tools by explaining that each chat's ref is the chat_id the other tools accept. An agent can tell this is the entry-point enumeration tool without opening the schema.

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?

'Use this first' gives an explicit usage directive relative to the other tools, and 'page with offset while has_more is true' supplies the continuation condition. It stops short of naming a specific alternative to use instead (e.g., list_folders or search_messages), so no exclusion criteria are stated.

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