Skip to main content
Glama

send_video_note

Send round video messages to Telegram chats using URL or file ID, with options for duration, size, and silent delivery.

Instructions

Send a video note (round video) to a Telegram chat.

Args: chat_id: Target chat ID. video_note_url: URL or file_id of the video note. duration: Duration in seconds. length: Video width and height (diameter of the circle). disable_notification: Send silently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chat_idYes
video_note_urlYes
durationNo
lengthNo
disable_notificationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
errorNo
chat_idNo
message_idNo

Implementation Reference

  • The implementation of the send_video_note tool, which handles the logic for sending a video note to a Telegram chat, including permissions, rate limiting, and execution via the bot context.
    async def send_video_note(
        chat_id: int,
        video_note_url: str,
        duration: int | None = None,
        length: int | None = None,
        disable_notification: bool = False,
    ) -> SendMediaResult:
        """Send a video note (round video) to a Telegram chat.
    
        Args:
            chat_id: Target chat ID.
            video_note_url: URL or file_id of the video note.
            duration: Duration in seconds.
            length: Video width and height (diameter of the circle).
            disable_notification: Send silently.
        """
        if not ctx.is_chat_allowed(chat_id):
            result = SendMediaResult(ok=False, error=f"Chat {chat_id} is not allowed.")
            if ctx.audit_logger:
                ctx.audit_logger.log(
                    "send_video_note",
                    {"chat_id": chat_id, "video_note_url": video_note_url},
                    result.ok,
                    result.error,
                )
            return result
    
        try:
            if ctx.rate_limiter:
                await ctx.rate_limiter.acquire()
            msg = await ctx.bot.send_video_note(
                chat_id=chat_id,
                video_note=video_note_url,
                duration=duration,
                length=length,
                disable_notification=disable_notification,
            )
            result = SendMediaResult(ok=True, message_id=msg.message_id, chat_id=msg.chat.id)
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose important behavioral aspects like authentication requirements, rate limits, error conditions, whether the operation is idempotent, or what happens on success/failure. The description is minimal beyond the core functionality.

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

Conciseness5/5

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

The description is perfectly structured and concise. The first sentence states the purpose clearly, followed by a well-organized Args section with bullet-like parameter explanations. Every sentence earns its place with no wasted words or redundancy.

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

Completeness3/5

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

For a 5-parameter mutation tool with no annotations, the description covers the basic action and parameters adequately. However, it lacks important context about behavioral aspects, error handling, and usage guidelines. The existence of an output schema reduces the need to describe return values, but more operational context would be helpful for this type of tool.

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?

With 0% schema description coverage, the description compensates well by explaining all 5 parameters in the Args section. Each parameter gets a clear semantic explanation: 'Target chat ID', 'URL or file_id of the video note', 'Duration in seconds', 'Video width and height (diameter of the circle)', and 'Send silently'. This adds significant value beyond the bare schema.

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?

The description clearly states the action ('Send a video note') and target ('to a Telegram chat'), with the parenthetical 'round video' providing helpful clarification about the format. It distinguishes this from other media-sending tools like send_video or send_photo by specifying the unique video note format.

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 is provided about when to use this tool versus alternatives like send_video or send_message. The description doesn't mention prerequisites, appropriate contexts, or limitations that would help an agent choose between this and sibling tools for similar media-sending tasks.

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/Py2755/aiogram-mcp'

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