SiteCheck Shop & Social

Latest public posts of one Telegram channel as shown on its

social_telegram_homepage

Read-only

Latest public posts of one Telegram channel as shown on its public web preview (t.me/s/): post id, text, view count text and date, about 20 per page. Only public channels with a preview; the Telegram homepage itself has no data, so this tool reads a channel's public feed. Related tools on this server, for a different need: social_telegram_channel when you need Public Telegram channel from its t.me/s preview page; 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_homepage"
  }
}

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
`checkedAt`	No
`postCount`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover read-only and open-world behavior, and the description adds material context beyond them: pagination of about 20 posts per page, the eligibility constraint (public channels with a preview only), and an explicit pricing model of $0.002 USDC per successful call via x402 with failed calls not charged. That cost disclosure is genuinely useful for an agent deciding whether to call. It stops short of describing pagination controls or rate limits.

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 opening sentences are front-loaded and informative, and the pricing note is worth its space. But the sibling section is awkwardly constructed, ends mid-thought with 'using.', and the statement that 'the Telegram homepage itself has no data' is a slightly redundant restatement of the public-preview constraint.

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 explained, and the description still summarizes them. Pricing, page size, and eligibility are all disclosed for a simple one-parameter scrape tool. The only real gap is a coherent statement of when to prefer this over social_telegram_channel.

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's description already specifies 'Public channel username without @ (5-32 letters, digits or _)'. The description's only addition is situating the value inside the t.me/s/<channel> URL pattern, which is mildly helpful. Baseline 3 applies since the schema does the heavy lifting.

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?

States a specific verb and resource (latest public posts of one Telegram channel), names the underlying source (t.me/s/<channel>), and lists what comes back (post id, text, view count, date) plus page size (~20). It attempts to distinguish itself from siblings, but the boundary with social_telegram_channel is left murky since that sibling is described almost identically as reading a t.me/s preview page.

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?

Provides a real constraint — 'Only public channels with a preview; the Telegram homepage itself has no data' — which tells the agent when this will fail. However, the alternative routing sentence is garbled ('social_telegram_keyword_search when you need keyword search inside one public Telegram channel, using.') and the social_telegram_channel differentiation does not state a condition that would actually select one over the other.

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?