telegram-mcp-server

Overview Schema Source Related Servers Discussions Admin

scrape_manual

Opens a browser for manual login and navigation to any Telegram channel, then scrapes its posts. Optionally save results to MD or JSON files.

Instructions

Manual scraping mode: Opens browser for you to login and navigate to any channel, then scrapes it

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": "scrape_manual"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of posts to scrape (optional)
`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.9/5.0

Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It does mention the interactive browser session and user-driven login/navigation. However, it does not mention output format, side effects like file saving, or any limitations, leaving some behavioral aspects undisclosed.

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 sentence, front-loaded with the tool's purpose, with no redundant 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?

The description is adequate for a simple interactive tool but lacks explicit details about what 'scrapes' returns, whether files are saved by default, and what happens after interaction. Given no output schema, a bit more detail would help.

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?

All parameters have schema descriptions, so the description need not add parameter details. It adds no extra semantics beyond the schema, meeting the baseline.

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 tool's function: manually scraping a channel by opening a browser for login and navigation. The phrase 'Manual scraping mode' distinguishes it from sibling tools like scrape_channel which likely automate the process.

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?

The description implies when to use it (when manual login/navigation is needed) but does not explicitly reference alternatives or when not to use automated tools. The context is clear but not fully exclusive.

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

Deploy Server