telegram-mcp

Overview Schema Source Related Servers Discussions Admin

export_chat

Export up to 1000 messages from a Telegram chat as JSON for archiving or analysis. Fetch chat history directly through the MCP server.

Instructions

Export messages from a chat as JSON (max 1000 per call)

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_id": "<chat_id>"
    },
    "name": "export_chat"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`chat_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Aug 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals the output format and a call limit, but does not state whether export modifies state, requires auth, has rate limits, or what happens beyond 1000 messages.

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?

The description is a single compact sentence with no filler; the primary action, resource, format, and limit are all front-loaded.

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?

For a simple two-parameter tool, the description covers the core behavior and limit. However, with no output schema and no annotations, it leaves open important operational details such as pagination behavior, response shape, and auth expectations.

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 must compensate. It relates 'chat' to the chat_id concept and the 1000 cap to the limit parameter, but never names chat_id or limit or explains types or formats, leaving room for misinterpretation.

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 specifies a clear verb-resource pair: 'Export messages from a chat', and adds output format JSON and a call limit. It does not explicitly name or distinguish itself from sibling export_cached_messages, so sibling differentiation is only implicit.

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?

No guidance is given on when to prefer this tool over export_cached_messages, get_message, or message_timeline. The 'max 1000 per call' phrase hints at pagination, but there is no when-to-use or when-not-to-use context.

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