Skip to main content
Glama
Telegram Live MCP

Telegram Live MCP

by sugestr

get_media

Read-only

Download any attachment from a specific Telegram message and return its local file path so you can inspect PDFs, scans, contracts, archives, videos, or other files outside the chat.

Instructions

Скачать вложение конкретного сообщения и вернуть путь к файлу на диске. Нужно, когда содержательное лежит не в тексте: счёт в PDF, скан, договор, архив, видео или файл любого типа. Номер сообщения берётся из выдачи read_chat — там медиа помечены как «msg 1234». Полный оригинал до фактического download-лимита Telegram кладётся на диск; открывай его дальше обычными средствами сессии.

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": {
      "chat_id": "<chat_id>",
      "message_id": "<message_id>"
    },
    "name": "get_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idYesиз find_dialogs
message_idYesномер сообщения из read_chat

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the original file is written to disk up to Telegram's actual download limit and should be opened with the session's ordinary means — useful side-effect and follow-up context that the readOnlyHint/openWorldHint annotations alone do not convey. It does not say what happens past that limit or when a message has no attachment, and writing a file to disk is a side effect that arguably sits at the edge of readOnlyHint=true (read as remote-state safety, not a true contradiction).

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

Conciseness4/5

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

Four short sentences, front-loaded with the action and result, then the trigger condition, then the source of the ID, then the disk/limit caveat. Minor redundancy in the tail of the file-type list ('видео или файл любого типа') is the only wasted wording.

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 two required parameters, a fully documented schema, and no output schema, the description covers action, trigger, ID provenance, return value, and disk/limit behavior — the important pieces for correct invocation. Error cases (no attachment on the message, exceeded download limit) are left implicit.

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

Parameters4/5

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

Schema coverage is 100%, so both parameters are already documented, but the description adds provenance value: chat_id comes from find_dialogs and message_id appears in read_chat output as «msg 1234». That marker convention is meaningfully more than the schema's 'номер сообщения из read_chat'.

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 first sentence states a precise verb and resource (download the attachment of a specific message) and adds the return value (a file path on disk). This is enough to distinguish it from read_chat, which returns text rather than files.

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?

It explicitly states when to use it: when the substantive content is not in the text (PDF invoice, scan, contract, archive, video, any file). It also names where the message_id comes from (read_chat output, marked as «msg 1234»), so the agent knows the required upstream step and which sibling to call first.

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