SiteCheck Shop & Social

Public Telegram channel from its t.me/s preview page

social_telegram_channel

Read-only

Public Telegram channel from its t.me/s preview page: title, description, subscriber/photo/video/link counts, and the latest ~20 posts with text, view count text and time. Only public channels that show a preview; private chats and groups are not returned. Related tools on this server, for a different need: social_telegram_homepage when you need latest public posts of one Telegram channel as shown on its; social_telegram_keyword_search when you need keyword search inside one public Telegram channel, using. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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

Input Schema

Name	Required	Description	Default
`channel`	Yes	Public channel username without @ (5-32 letters, digits or _)

Output Schema

Name	Required	Description	Default
`posts`	No
`source`	No
`channel`	No
`counters`	No
`checkedAt`	No
`postCount`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely new behavioral facts beyond them: the ~20-post recency cap, the public-preview-only coverage limit, and the pricing model ($0.002 USDC per successful call via x402 on Base, Solana or Arc, with failed calls not charged). Cost and failure-charging behavior are exactly the kind of detail an agent needs before invoking a paid tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The payload and coverage statement are front-loaded, which is good, but the sibling-routing sentences are syntactically broken and trail off, and the pricing sentence is dense. The information earns its place, yet the phrasing is awkward enough to slow parsing.

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?

With an output schema present, return-value explanation is unnecessary, and the description covers scope, coverage limits, post cap and billing. It does not address error cases for invalid or private channel names or any rate limits, which is a modest remaining gap for a single-parameter paid tool.

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 coverage is 100% and the single parameter already documents that the channel username must omit '@' and be 5-32 letters, digits or underscores. The description adds no format or validation detail beyond the schema, so the baseline 3 applies even though no gap exists.

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 opens with a specific verb-and-resource statement: it retrieves a public Telegram channel from its t.me/s preview page and enumerates exactly what comes back (title, description, subscriber/photo/video/link counts, latest ~20 posts with text, view count text and time). This is clearly distinguishable from social_telegram_homepage and social_telegram_keyword_search, which are named as different-need alternatives.

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 states an explicit eligibility boundary — only public channels that show a preview, with private chats and groups not returned — and routes the agent to two named siblings for adjacent needs. The routing clauses are truncated/garbled ('as shown on its;', 'using.'), which weakens but does not remove the when-to-use guidance.

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

All SiteCheck Shop & Social tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?