Skip to main content
Glama
ClearStack Data MCP server

ClearStack Data MCP server

by Wordhalm

Read public Telegram channels

get_telegram_channel_posts
Read-only

Retrieve recent public Telegram channel posts without a Telegram account, including text, dates, views, reactions, links, and hashtags; apply keyword and date filters.

Instructions

Fetch recent posts from public Telegram channels without a Telegram account: text, date, views, reactions, links, hashtags. Optional keyword filter and date cutoff. Cost on the user's Apify account: $0.002 per call + $0.0015 per post returned.

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

Input Schema

NameRequiredDescriptionDefault
channelsYesChannel usernames or URLs: "durov", "@telegram", "https://t.me/bloomberg".
keywordsNoOnly posts containing any of these words (case-insensitive).
sinceDateNoOptional date (YYYY-MM-DD); older posts are skipped.
maxPostsPerChannelNoNewest posts first.

Output Schema

NameRequiredDescriptionDefault
actorYesApify Actor that produced the data
itemsYes
runIdYesApify run ID; pass it to get_run_results if finished is false
statusYesApify run status, e.g. SUCCEEDED or RUNNING
finishedYesfalse when the run was still going and items are partial
itemCountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds context annotations cannot carry: no Telegram credentials needed and an explicit cost model ($0.002 per call + $0.0015 per post), which materially affects how an agent should batch or throttle calls. It stops short of describing rate limits 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 sentences, zero filler. The highest-value facts — no account needed, what is returned, and the price — are front-loaded, with the filtering note and cost last where an agent will still see them before calling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be re-explained, yet the description still names the key fields. Combined with disclosure of the authentication requirement and per-call cost, an agent has everything needed to invoke this tool correctly and budget it.

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 schema already explains channel formats, keyword matching (case-insensitive) and the YYYY-MM-DD cutoff. The description restates only that a keyword filter and date cutoff are optional, adding no new syntax or constraints beyond the structured fields. Baseline 3 applies 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?

States a specific verb and resource ('Fetch recent posts from public Telegram channels') and immediately enumerates the payload ('text, date, views, reactions, links, hashtags'). The qualifier 'without a Telegram account' further pins down the scope, so an agent knows exactly what it gets back.

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?

Usage is only implied: it tells the agent that no Telegram account is required and that keyword/date filters exist, but never says when to reach for this tool versus anything else. With no explicit when-to-use or when-not-to-use statement, the agent must infer the context.

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