Skip to main content
Glama
paulet4a-commits

webdatatools-social-mcp

by paulet4a-commits
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

telegram_channel_scraper

Scrape public Telegram channels via t.me/s/ to extract post text, view counts, media flags, forwards, replies and links. No API key or login required.

Instructions

Scrapes public Telegram channels via the t.me/s/ web preview — post text, view counts, media flags, forwards, replies and links, one row per post, no API key or login required. Billed to your own Apify account: ~$0.0005 per Post (Apify free-plan price, lower on paid plans).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelsYesChannels — Enter one public Telegram channel per row: a bare handle (telegram), an @handle (@telegram) or a t.me URL (https://t.me/telegram). The channel must have public content preview enabled at t.me/s/<handle> — private channels and groups are not supported. Example: ["@telegram"].
maxPostsNoMax posts per channel — Enter how many of the most recent posts to fetch per channel, e.g. 50. The Actor pages through https://t.me/s/<channel>?before=<id> until this many posts are collected.
includeTextNoInclude post text — Keep this on to include each post's message text and the links found inside it. Turning it off leaves text and links empty, which is faster when you only need view counts and media flags.
newestFirstNoNewest posts first — Keep this on to sort each channel's rows from newest to oldest post. Turn it off for oldest-first order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the scraping mechanism (t.me/s web preview), that no auth is needed, output granularity (one row per post) and the billing model (~$0.0005 per Post). It stops short of rate limits, failure modes when preview is disabled, or pagination behavior.

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 tightly packed sentences with zero filler. The capability and mechanism are front-loaded, and the billing caveat is placed last where it belongs.

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?

With 4 well-documented parameters and no output schema, the description usefully enumerates returned fields (text, view counts, media flags, forwards, replies, links), filling the output gap. Only edge-case behavior (blocked previews, partial failures) is unaddressed.

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 the baseline is 3. The description adds only the per-post cost framing and output shape ('one row per post'), which lightly informs maxPosts but contributes no syntax or format 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?

Starts with a specific verb and resource ('Scrapes public Telegram channels') and immediately names the mechanism (the t.me/s/ web preview), which distinguishes it cleanly from the YouTube, podcast, Bluesky and Substack siblings. An agent can identify this tool from the first clause alone.

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?

Gives clear conditions: public channels only, no API key or login required, billing accrues to your own Apify account. The exclusion of private channels/groups appears in the schema, so the description covers context without explicit when-not routing or named alternatives.

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