Skip to main content
Glama
Sign In
adhistory-mcp

adhistory-mcp

by OBrandon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Public Telegram channel posts

telegram_posts
Read-onlyIdempotent

Read recent posts from public Telegram channels and filter them by keywords, age, and views to analyze content and engagement.

Instructions

Read recent posts from public Telegram channels (the t.me/s web preview; no login, private channels and groups cannot be read). Each item: channel, post link and id, text, date, views, reactions, links, hashtags, mentions, emails, media flags, channel subscribers, plus analysis: views vs the channel's median (viewsVsMedian), view rank, view and reaction rate, weekday and hour. Filter by keywords, age and minimum views. Newest posts first; only what Telegram shows publicly. Cost: $0.35 per 1,000 posts on the user's Apify account; the default 20 posts cost $0.007. Latency: usually 5-30 s.

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

Input Schema

NameRequiredDescriptionDefault
channelsYesPublic channels: username (durov), @username or https://t.me/name link.
max_itemsNoStop after this many posts in total.
min_viewsNoOptional. Keep posts with at least this many views.
search_textNoOptional. Keep posts whose text contains all these words.
posted_within_daysNoOptional. Stop at posts older than this many days.
max_posts_per_channelNoNewest posts to read per channel.
only_new_since_last_runNoSkip posts returned by an earlier run on this Apify account.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, yet the description adds cost ($0.35 per 1,000 posts, $0.007 for the default 20), latency (5-30 s), sort order (newest first), and the public-visibility constraint. Those are the facts an agent needs to decide whether calling is worth it, and none are derivable from annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the source and access constraint, then output shape, then filtering, then cost/latency — a sensible ordering. The enumerated field list ('channel, post link and id, text, date, views, reactions...') is long and largely redundant with the output schema, which costs it a point.

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?

For a 7-parameter scraping tool with an output schema, the description covers access model, filtering semantics, ordering, cost, and latency. The output-schema redundancy is excess rather than a gap, and nothing needed to invoke it correctly is missing.

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 is already documented in the schema. The description only groups the filters ('keywords, age and minimum views') without adding format, interaction, or precedence detail, so baseline 3 applies.

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 ('Read recent posts from public Telegram channels') and immediately bounds scope with 't.me/s web preview; no login, private channels and groups cannot be read'. An agent knows exactly what data source and access path this tool uses, and no sibling tool overlaps with Telegram content.

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?

Explicitly states what cannot be read (private channels, groups) and what filters are available for narrowing results, which tells the agent when this tool applies. It does not name an alternative tool or an explicit 'when not to use' branch, but the exclusion of private sources covers the main mis-selection risk.

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