Retrieve average post reach for a Telegram channel over a chosen date range, grouping results by hour, day, week, or month to analyze engagement trends.
Average post-reach history of a channel over time.
| Name | Required | Description | Default |
|---|---|---|---|
| group | No | Grouping period | day |
| end_date | No | Range end (YYYY-MM-DD) | |
| channel_id | Yes | Channel @username / t.me link / TGStat ID | |
| start_date | No | Range start (YYYY-MM-DD) |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, and the description does not disclose side effects, return behavior, data source, or limitations. Since it is a read-like operation the risk is low, but the description carries the full burden and does not elaborate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single clear sentence with no unnecessary words. It is appropriately sized and front-loaded with the core purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has no output schema and the description does not specify the response format, units, or whether the average is computed per post or per period. The parameter set covers the main inputs, but return semantics are left implicit.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema covers all four parameters with concise descriptions: channel_id format, date patterns, and grouping period. However, it does not explain whether start_date/end_date are both required for a meaningful range or how the default group 'day' affects the returned history.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly identifies the resource (a channel) and metric (average post-reach) over time. It is distinguishable from siblings like get_channel_stats or get_channel_views, though it is phrased as a noun phrase rather than an explicit verb.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus related tools such as get_channel_stats, get_channel_views, or get_channel_posts. The description does not mention preferred use cases or conditions that would make this tool the right choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.