Skip to main content
Glama
theYahia

@theyahia/tgstat-mcp

by theYahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_channel_posts

Fetch recent posts from a Telegram channel with view metrics, filterable by date range and pagination.

Instructions

Get recent posts of a channel with view metrics. Supports an optional date range and pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPosts to return (max 50)
offsetNoPagination offset (max 1000)
end_dateNoOnly posts on/before this date (YYYY-MM-DD)
extendedNoInclude the channel object in the response
channel_idYesChannel @username / t.me link / TGStat ID
start_dateNoOnly posts on/after this date (YYYY-MM-DD)
hide_forwardsNoExclude reposts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changedv2.0.0
    • changedInput schema / properties / channel_id / description
      Previous value: -"ID или username канала"New value: +"Channel @username / t.me link / TGStat ID"
    • addedInput schema / properties / channel_id / minLength
      Added value: +1
    • addedInput schema / properties / end_date
      Added value: +{
+  "description": "Only posts on/before this date (YYYY-MM-DD)",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • addedInput schema / properties / extended
      Added value: +{
+  "default": false,
+  "description": "Include the channel object in the response",
+  "type": "boolean"
+}
    • addedInput schema / properties / hide_forwards
      Added value: +{
+  "default": false,
+  "description": "Exclude reposts",
+  "type": "boolean"
+}
    • addedInput schema / properties / limit / default
      Added value: +20
    • changedInput schema / properties / limit / description
      Previous value: -"Количество постов (по умолчанию 20)"New value: +"Posts to return (max 50)"
    • addedInput schema / properties / limit / maximum
      Added value: +50
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / offset / default
      Added value: +0
    • changedInput schema / properties / offset / description
      Previous value: -"Смещение для пагинации"New value: +"Pagination offset (max 1000)"
    • addedInput schema / properties / offset / maximum
      Added value: +1000
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / start_date
      Added value: +{
+  "description": "Only posts on/after this date (YYYY-MM-DD)",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
  2. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the burden of explaining behavior. It does mention the return type (posts with view metrics) and supported options (date range, pagination), but it omits details like sorting order, output shape, error handling, and whether date boundaries are inclusive. This is adequate but not fully transparent.

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?

The description is two concise sentences with no redundant phrases or extraneous details. It efficiently communicates the core purpose and key optional capabilities.

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?

Given the absence of an output schema and annotations, the description provides a reasonable high-level summary but lacks important context such as response structure, default sort order, pagination behavior, or date range inclusivity. It is not incomplete enough to be misleading, but it leaves room for interpretation.

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?

The JSON schema already provides descriptions for all 7 parameters, covering 100% of them. The tool description adds only a high-level mention of optional date range and pagination, which does not materially enhance understanding beyond the schema definitions. Baseline score of 3 is appropriate.

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?

The description clearly states a specific action ('Get') on a specific resource ('posts of a channel') and includes key modifiers (recent, with view metrics, optional date range and pagination). This distinguishes it from sibling tools like get_channel_forwards, get_channel_mentions, and get_post without ambiguity.

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?

The description does not provide any explicit guidance on when to use this tool versus its alternatives, such as get_channel_forwards, get_channel_mentions, or search_posts. It merely restates the purpose without contrasting with related tools or indicating appropriate scenarios.

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