Skip to main content
Glama
GeiserX

telegram-archive-mcp

by GeiserX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Remote

get_messages_by_date

Read-only

Retrieve every Telegram chat message sent on one calendar day, oldest first, using the specified timezone.

Instructions

Get every message of a Telegram chat sent on one calendar day, oldest first. The day is taken in the given timezone (default UTC); the archive stores dates in UTC. Walks the chat with the keyset cursor, so it is cheap even on chats with hundreds of thousands of messages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate in YYYY-MM-DD format
limitNoMaximum messages to return (default 1000, max 5000). When the day has more, the newest are dropped and truncated is true.
chat_idYesChat ID to retrieve messages from
timezoneNoIANA timezone the date is expressed in (e.g. Europe/Madrid). Default UTC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.3
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Maximum messages to return (default 1000, max 5000). When the day has more, the newest are dropped and truncated is true.",
+  "type": "number"
+}
    • changedInput schema / properties / timezone / description
      Previous value: -"IANA timezone (e.g. Europe/Madrid). Optional."New value: +"IANA timezone the date is expressed in (e.g. Europe/Madrid). Default UTC."
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With readOnlyHint already declaring the safety profile, the description adds real behavioral context beyond annotations: oldest-first ordering, timezone vs. UTC archive storage, and keyset-cursor efficiency on very large chats. It stops short of describing truncation/pagination at the description level, though the schema covers the limit case.

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?

Two sentences, purpose front-loaded, zero filler; the timezone and efficiency notes are compact and each earns its place.

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?

For a read-only, 4-parameter tool with full schema coverage and no output schema, the description supplies the ordering, timezone semantics, and cost model an agent needs. Only truncation/limit behavior is left entirely to the schema.

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%, so the baseline is 3, but the description adds meaning the schema does not: that the day is interpreted in the supplied timezone while the archive stores UTC, clarifying how date/timezone interact. It adds little on limit beyond what the schema already documents.

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 (Get), resource (every message of a Telegram chat), and tight scope (one calendar day, oldest first). It clearly differentiates from the generic get_messages by the day-scoping and ordering, but never names a sibling explicitly.

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 day-scoped framing implies when this tool applies versus a general message fetch, but there is no explicit when-to-use/when-not guidance and no alternative (e.g. get_messages or search_messages) is named for other cases.

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