Skip to main content
Glama
zrk-scrapers-mcp

zrk-scrapers-mcp

by Zrk1212

Telegram Channel Scraper

scrape_telegram_channel

Collect posts and subscriber stats from public Telegram channels, including text, views, reactions, media, and comment counts, without login.

Instructions

Scrape posts from public Telegram channels: text, views, reactions, media and comment counts, plus a stats row with exact subscriber count. No login needed. Priced per post. Runs the Apify actor zrk1212/telegram-channel-scraper-stats on your Apify account.

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": {
      "channels": "<channels>"
    },
    "name": "scrape_telegram_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelsYesChannel usernames or t.me links, e.g. ['durov'].
dateFromNoOnly posts on or after YYYY-MM-DD.
maxItemsNoMost result rows to return in this response (default 50). The run may produce more; page with get_run_results.
waitSecsNoSeconds to wait for the run to finish (default 120). If it is still running, use get_run_results later.
extraInputNoAny other input field of the Apify actor zrk1212/telegram-channel-scraper-stats, passed through as-is. See https://apify.com/zrk1212/telegram-channel-scraper-stats/input-schema
searchQueryNoOnly posts matching this search.
maxChargeUsdNoHard spending cap for this run in USD (default 1). Apify stops charging when it is reached.
maxPostsPerChannelNoRecent posts per channel (default 50).
includeChannelStatsNoAdd a channel stats row (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

The annotations only declare the generic profile (not read-only, open-world, non-idempotent, non-destructive); the description adds genuinely new behavioral context: no authentication required, per-post billing, and that the run executes a named Apify actor on the caller's account. It stops short of disclosing run lifecycle behavior (long-running runs, timeouts, re-runs producing duplicates), which is the remaining gap.

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?

Four short sentences, front-loaded with the capability and payoff, followed by auth, pricing and execution context. No filler, no repetition of the title, and each sentence adds a distinct fact.

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 9-parameter, nested-input scraping tool with no output schema, the description conveys the return payload shape well enough and covers cost/auth expectations. The missing piece is run lifecycle and result-paging behavior, which the schema hints at (waitSecs, get_run_results) but the description never states.

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 description coverage is 100%, so every parameter including nested extraInput is already documented in the schema. The description only indirectly illuminates semantics (per-post pricing ties to maxChargeUsd, the stats row ties to includeChannelStats) without adding syntax or defaults. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

Names a specific verb and resource ('Scrape posts from public Telegram channels') and enumerates the returned data: text, views, reactions, media, comment counts and a subscriber-stats row. This is far more specific than sibling tools operating on entirely different sources (ATS jobs, Google Ads, PageSpeed), so an agent can route to it 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Useful preconditions are stated ('No login needed', 'Priced per post', runs on your Apify account), which helps an agent decide whether it can call it. However, there is no explicit when-to-use/when-not guidance and no mention of the asynchronous run pattern (waiting via waitSecs and paging with get_run_results) that would shape how an agent invokes it.

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