telemost-mcp-server

telemost_post

telemost_post

Read-onlyIdempotent

Analyze a specific Telegram post's performance over time, including views, forwards, and reactions. Get detailed stats with pay-per-call pricing in USDC.

Instructions

Telegram post analytics: a single post with its statistics over time, views, forwards and reactions. Measure how a specific post performed. Paid per call in USDC from your wallet (see telemost_catalog for the price).

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": {
      "post": "<post>"
    },
    "name": "telemost_post"
  }
}

Input Schema

Name	Required	Description	Default
`post`	Yes
`region`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.2Aug 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds meaningful behavior: 'Paid per call in USDC from your wallet (see telemost_catalog for the price).' This cost disclosure is valuable and goes beyond the structured annotations.

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?

Two sentences, front-loaded with the core purpose, followed by a cost warning. Every sentence adds value; there is no fluff or repetition.

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?

The description covers the main function and cost, but lacks parameter semantics and expected response format. With no output schema and two parameters (one with an enum), the agent needs more details on how to specify the post and region. It is adequate but has clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate for parameter meaning. It does not explain what 'post' expects (URL, ID, username) nor what 'region' ('cis' vs 'worldwide') means. The mention of 'a single post' in the description gives minimal context, but not enough for correct invocation.

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 states a specific verb ('Measure') and resource ('a single post') with clear scope: 'statistics over time, views, forwards and reactions.' This distinguishes it from siblings like telemost_posts_search or telemost_stats_engagement, which focus on discovery or broader engagement metrics.

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?

It provides clear context: 'Measure how a specific post performed.' This implies use when you need post-level analytics. However, it does not explicitly exclude alternatives or name sibling tools for other use cases, so it stops short of a 5.

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