SiteCheck Shop & Social

Keyword search inside one public Telegram channel, using

social_telegram_keyword_search

Read-only

Keyword search inside one public Telegram channel, using the channel's own preview search: matching posts with id, text, view count text and date (about 20 per page). It cannot search across all of Telegram; private chats and groups are not searchable here. 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_homepage when you need latest public posts of one Telegram channel as shown on its. 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>",
      "query": "<query>"
    },
    "name": "social_telegram_keyword_search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Keyword or phrase to search for (2-100 characters)
`channel`	Yes	Public channel username without @ (5-32 letters, digits or _)

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations cover only readOnlyHint and openWorldHint, but the description adds what those cannot: page size (~20 per page), the materialized fields, the billing model ($0.002 per successful call, failures not charged) and the payment rails. Cost-per-call and no-charge-on-failure are exactly the operational facts an agent needs before invoking a paid endpoint.

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 core purpose is front-loaded and earns its place, but the sibling pointer sentences are grammatically broken ('as shown on its.' trails off), which weakens a section that is otherwise the routing mechanism. The pricing boilerplate is lengthy for what it conveys, so the paragraph is longer than needed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with an output schema and read-only annotations, the description supplies everything missing: scope limits, page size, result shape, sibling routing and the paid-call terms. Nothing an agent needs to call it correctly is absent.

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%: both parameters already document format and length constraints (2-100 characters for the query, 5-32 characters without @ for the channel). The description adds only the framing that the search runs on the channel's preview index, which is context rather than parameter meaning. Baseline 3 applies.

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?

States a specific verb and resource with scope: 'Keyword search inside one public Telegram channel, using the channel's own preview search.' It also names the returned fields and immediately rules out the most likely misreading ('cannot search across all of Telegram'). An agent can tell this apart from social_telegram_channel and social_telegram_homepage without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit exclusions are given ('private chats and groups are not searchable here') plus the alternative tool with its condition for each sibling ('social_telegram_channel when you need...', 'social_telegram_homepage when you need...'). This is close to the ideal when/when-not/alternatives pattern.

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?