Social Data
Información de un canal de Telegram MCP
Use Consulta la información de un canal de Telegram. in your AI assistant to retrieve the available information. Explore supported inputs and use cases below.
Información de un canal de Telegram AI Prompts & Use Cases
After connecting this MCP tool to your AI assistant, you can ask the questions below. Replace bracketed placeholders with your own inputs and use the supported values in Arguments.
New to Nexscope MCP? Follow the connection guide, then use the prompts below. The Integration and Parameters & Response tabs contain the connection steps, call example, and technical reference.
1. Review Telegram Channel Details
Prompt: Retrieve Telegram Channel Details for [account handle]. Summarize only the information actually returned and preserve source links when available. Report private, restricted, missing or partial results explicitly; missing values are not zero.
2. Create A Brief From Returned Text
Prompt: Retrieve Telegram Channel Details for [account handle] and prepare a brief about [my research question] using only text present in the response. Cite the corresponding source links when returned, distinguish quotations from interpretation, and report insufficient text. Do not claim to have read linked pages or infer private information.
3. Inspect A Public Channel’S Content Mix
Prompt: Retrieve [public Telegram channel handle or URL] and show its reported photo, video, file and link counters alongside its subscriber or member count. Keep each counter’s label and missing values explicit. Do not infer unique messages, a time trend or private-group activity from these totals.
What You Need to Provide
Use only the documented public inputs. Private, restricted, missing and partial results remain distinct; missing metrics are not zero.
Check the current Nexscope price before running the request. Optional enrichment, downloads, transcription and additional pages can incur charges. These examples do not execute a request.
Step 1 · Connect
Connect Your AI Assistant
Connect a compatible MCP client to Nexscope, then select this tool from your assistant. Use the connection settings in your client to complete authentication.
POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/jsonAutenticación
Usa el código de autorización OAuth 2.1 con PKCE y el ámbito mcp:tools. Las claves de API siguen siendo una opción de compatibilidad admitida.
Authorization: Bearer nk-xxxxxxxxxxxxxxxxxUsing an API key? Get your key from API Access and include it in the Authorization header shown above.
Llamar a esta herramienta MCP
social_telegram_channelhttps://api.nexscope.ai/mcptools/callInicializa una sesión HTTP Streamable MCP 2025-11-25 en https://api.nexscope.ai/mcp y después usa tools/call.
{
"jsonrpc": "2.0",
"id": "social-telegram-channel-1",
"method": "tools/call",
"params": {
"name": "social_telegram_channel",
"arguments": {
"handle": "telegram"
}
}
}MCP 2025-11-25 · Streamable HTTPEl progreso se entrega en la respuesta SSE del POST original. GET SSE transporta las notificaciones; al reconectarse se debe consultar el trabajo asíncrono existente en lugar de enviarlo de nuevo.
Argumentos
| Nombre | Tipo | Obligatorio | Descripción |
|---|---|---|---|
handle | string | obligatorio | Public Telegram handle, @handle, or t.me channel URL. Ejemplo: telegram |
cache_max_age | string | opcional | If we have a response in the cache that is this many days old or newer, return the cached response (0 credits, with "cached": true and a "cached_at" timestamp). Otherwise, scrape a live result (1 credit). [See the Caching page for details.](https://docs.scrapecreators.com/caching) |
Campos de respuesta
Usa structuredContent como los datos de respuesta de la API para el procesamiento programático.
| Nombre | Tipo | Obligatorio | Descripción |
|---|---|---|---|
code | integer | obligatorio | 0 means accepted or successful; nonzero is a platform error. |
cost | string | obligatorio | Elapsed milliseconds, never credits; -1 outside web requests. |
data | any | obligatorio | Valor de Data usado por esta operación de API. |
msg | string | null | obligatorio | Valor de Msg usado por esta operación de API. |
time | string | obligatorio | Server local time: yyyy-MM-dd HH:mm:ss. |
traceId | string | null | obligatorio | Valor de Trace id usado por esta operación de API. |
ts | string | obligatorio | Epoch milliseconds. |
Opción 1 de cualquier alternativa — requiere platform, resourceStatus, data, usage
| Nombre | Tipo | Obligatorio | Descripción |
|---|---|---|---|
data | object | obligatorio | Valor de Data usado por esta operación de API. |
data.data | object | obligatorio | Valor de Data usado por esta operación de API. |
data.platform | string | obligatorio | Valor de Platform usado por esta operación de API. |
data.resourceStatus | string | obligatorio | Valor de Resource status usado por esta operación de API. |
data.usage | object | obligatorio | Valor de Usage usado por esta operación de API. |
Opción 2 de cualquier alternativa
| Nombre | Tipo | Obligatorio | Descripción |
|---|---|---|---|
data | null | obligatorio | Valor de Data usado por esta operación de API. |
Workflow Guide
Workflow example, not a verified API response.
Your Goal
Retrieve Telegram Channel Details for [account handle]. Summarize only the information actually returned and preserve source links when available. Report private, restricted, missing or partial results explicitly; missing values are not zero.
Suggested Steps
Provide the documented public identifiers or search inputs. The assistant can then make the requested lookup and organize only the returned evidence. Missing or restricted results must be reported explicitly; no actual lookup or returned metrics are claimed here.
About this sample: Workflow example based on the published API document, not a live API response.
Published sample data is not available for this page. A format illustration or workflow guide is not a substitute for a published result.
View the MCP Request & Response Format
Ejemplos
Workflow example, not a verified API response.
The JSON-RPC envelope below illustrates how the shown arguments and payload fit into MCP. It is not captured network traffic or proof of a successful call. Workflow-only examples do not include a result.
MCP Request
No verified MCP request example is available. Refer to Integration and the documented requirements before preparing a call.
MCP Response Format
This workflow does not claim an API result. No verified response example is available; refer to Parameters & Response for the documented response structure.