Skip to main content
Glama
telegram-channels-mcp

telegram-channels-mcp

top_posts

Read-only

Retrieve a channel's best posts from the last N days, ranked by views, reactions, forwards, or comments, to identify top-performing content quickly.

Instructions

Best posts of a channel for the last N days, ranked by views, reactions, forwards or comments

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": {
      "channel": "<channel>"
    },
    "name": "top_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
limitNo
channelYes
sort_byNoviews

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context — that results are a ranked top-N over a rolling day window, with the ranking axis configurable — but says nothing about how ties, sparse reactions, or the returned count behave. With annotations doing the heavy lifting, this is adequate but not rich.

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?

A single front-loaded sentence that introduces the resource, the window, and the ranking options with zero filler. Nothing could be removed without losing 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?

With only four parameters, an output schema, and full annotations, the definition is close to sufficient, but the unexplained 'limit' and the absence of any usage routing leave a small gap. Adding one clause about result count and when to prefer this over search_messages would make it complete.

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 0%, so the description must carry parameter meaning; it does cover 'channel', 'days' ('last N days') and the sort_by enum values by name. However, 'limit' is never mentioned, so the size of the returned set (default 5) is undocumented anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource ('best posts of a channel') plus scope ('last N days') and a ranking dimension. It is immediately distinguishable from siblings like channel_stats or search_messages, though it never names an alternative explicitly to draw that boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of when not to use it or which sibling to pick instead (e.g. search_messages for arbitrary filtering). The only implied cue is the time-window/ranking framing, which is barely more than restating the tool's purpose.

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