Skip to main content
Glama
telegram-channels-mcp

telegram-channels-mcp

channel_stats

Read-only

Retrieve subscriber count, post views, reactions, average and median views, engagement rate, and posting frequency for public Telegram channels to analyze performance.

Instructions

Channel statistics: subscribers, views and reactions of the last N posts, average and median views, engagement rate and posting frequency. Works for any public channel, best for the user's own ones

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

Input Schema

NameRequiredDescriptionDefault
postsNo
channelYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, non-destructive, open-world operation. The description adds that it works for public channels and is best for the user's own channels, but it does not discuss authentication, 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.

Conciseness4/5

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

The description is compact and front-loads the main purpose with an efficient list of returned metrics. The phrase 'best for the user's own ones' is slightly awkward, but overall there is little wasted wording.

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?

An output schema exists, so return values need not be fully explained. The description covers the public-channel scope and the key metrics, though the missing channel identifier format leaves a small gap for invocation correctness.

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 clarify the two parameters. It explains that 'posts' means the last N posts and that 'channel' refers to a public channel, but it does not specify the accepted channel identifier format such as username, ID, or URL.

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 names the resource and the specific statistics returned: subscribers, views, reactions, average and median views, engagement rate, and posting frequency. It is clearly a channel-statistics tool, though it does not explicitly differentiate itself from siblings such as top_posts.

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?

It gives useful context by saying it works for any public channel and is best for the user's own ones. However, it does not state when to prefer alternatives like top_posts or get_comments, nor does it provide exclusions beyond the public-channel scope.

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