telegram-mcp-server

Overview Schema Source Related Servers Discussions Admin

scrape_channel_full

Scrape all posts from a Telegram channel and save to Markdown and JSON files. Returns the file location of the saved data.

Instructions

Scrape ALL posts from a Telegram channel and save to file. Uses authenticated session if logged in. Returns file location.

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": {
      "url": "<url>"
    },
    "name": "scrape_channel_full"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	The Telegram channel URL (e.g., https://t.me/channelname)
`save_to_file`	No	Save results to MD and JSON files

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Aug 10, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description must carry the burden of behavioral disclosure. It mentions using an authenticated session if logged in and returning the file location, which adds context. However, it omits side effects like file creation details, rate limits, or whether authentication is required, so transparency is partial.

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 two concise sentences, front-loaded with the main action and resource, and contains no redundant or extraneous information.

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?

Given the tool's scale (scraping all posts) and the lack of an output schema or annotations, the description provides the core action and return value but misses important context such as potential volume, prerequisites, limitations, and what 'ALL' includes. It is adequate but not fully complete.

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% with both parameters having descriptions. The tool description adds limited extra meaning—chiefly clarifying that 'ALL posts' means the full history and that saving is involved—but does not substantially enhance understanding beyond the schema.

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?

The description clearly states the action ('Scrape ALL posts') and the resource ('Telegram channel'), and the inclusion of 'ALL' distinguishes it from date-range or limited scrape tools. It also specifies the output behavior (save to file), making the purpose unambiguous.

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 word 'ALL' implies use when a full archive is needed, but there is no explicit guidance on when to choose this tool over alternatives like scrape_date_range or scrape_channel. No exclusions or alternative recommendations are provided.

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

Deploy Server