Skip to main content
Glama
al-one

MCP Server for notify to weixin / telegram / bark / lark

Telegram send video

tg_send_video

Send video messages to Telegram using a bot. Supports optional cover image, caption with parse modes, and reply to specific messages.

Instructions

Send video via telegram bot

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
videoYesVideo URL or base64 data URI (e.g., data:video/mp4;base64,...
coverNoCover for the video in the message. Optional
chat_idNoTelegram chat id, Default to get from environment variables
captionNoVideo caption, 0-1024 characters after entities parsing
parse_modeNoMode for parsing entities in the caption. [text/MarkdownV2]
reply_to_message_idNoIdentifier of the message that will be replied to

Implementation Reference

  • The `tg_send_video` async function that executes the tool logic. It accepts a video URL or base64 data URI, optional cover, chat_id, caption, parse_mode, and reply_to_message_id. It handles base64 decoding, then calls `bot.send_video()` and returns the result as JSON.
    async def tg_send_video(
        video: str = Field(description="Video URL or base64 data URI (e.g., data:video/mp4;base64,..."),
        cover: str = Field("", description="Cover for the video in the message. Optional"),
        chat_id: str = Field("", description="Telegram chat id, Default to get from environment variables"),
        caption: str = Field("", description="Video caption, 0-1024 characters after entities parsing"),
        parse_mode: str = Field("", description=f"Mode for parsing entities in the caption. [text/MarkdownV2]"),
        reply_to_message_id: int = Field(0, description="Identifier of the message that will be replied to"),
    ):
        if parse_mode == TELEGRAM_MARKDOWN_V2:
            caption = telegramify_markdown.markdownify(caption)
    
        if video.startswith("data:"):
            match = re.match(r"data:video/([^;]+);base64,(.*)", video)
            if not match:
                return {"error": "Invalid base64 data URL format"}
            try:
                datas = base64.b64decode(match.group(2))
                video = InputFile(io.BytesIO(datas), f"video.{match.group(1)}")
            except Exception as e:
                return {"error": f"Failed to decode base64: {str(e)}"}
    
        res = await bot.send_video(
            chat_id=chat_id or TELEGRAM_DEFAULT_CHAT,
            video=video,
            cover=cover or None,
            caption=caption or None,
            parse_mode=parse_mode if parse_mode in [TELEGRAM_MARKDOWN_V2] else None,
            reply_to_message_id=reply_to_message_id or None,
        )
        return res.to_json()
  • The `@mcp.tool()` decorator registering the tool with title 'Telegram send video' and description 'Send video via telegram bot'.
    @mcp.tool(
        title="Telegram send video",
        description="Send video via telegram bot",
    )
  • Pydantic Field definitions for the tool's parameters: video (str), cover (str), chat_id (str), caption (str), parse_mode (str), reply_to_message_id (int).
        video: str = Field(description="Video URL or base64 data URI (e.g., data:video/mp4;base64,..."),
        cover: str = Field("", description="Cover for the video in the message. Optional"),
        chat_id: str = Field("", description="Telegram chat id, Default to get from environment variables"),
        caption: str = Field("", description="Video caption, 0-1024 characters after entities parsing"),
        parse_mode: str = Field("", description=f"Mode for parsing entities in the caption. [text/MarkdownV2]"),
        reply_to_message_id: int = Field(0, description="Identifier of the message that will be replied to"),
    ):
  • Registration call `tgbot.add_tools(mcp)` which adds all telegram tools including tg_send_video to the MCP server.
    tgbot.add_tools(mcp)
Behavior2/5

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

No annotations exist, so description must cover behavioral traits. It only says 'send video' with no details on limitations (e.g., video size, format, permissions) or side effects.

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?

One short, direct sentence that conveys the core action. No wasted words, though it could be more informative without losing conciseness.

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

Completeness2/5

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

With 6 parameters, no output schema, and no annotations, the description is insufficient. It lacks details on return values, error handling, and usage context for a tool of this complexity.

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 description coverage is 100%, so baseline is 3. The description adds no extra meaning beyond what the parameter descriptions already provide.

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?

Description states 'Send video via telegram bot' – clear verb and resource. However, it does not differentiate from sibling tools like tg_send_photo or tg_send_audio, which also send media types.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives, no prerequisites or context provided. Agent has no help deciding between tg_send_video and other media-sending tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/al-one/mcp-notify'

If you have feedback or need assistance with the MCP directory API, please join our Discord server