aiogram-mcp

Overview Schema Source Related Servers Discussions Admin

send_video_note

Send a round video note to a Telegram chat by providing the chat ID and video URL. Optionally set duration, size, or send silently.

Instructions

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

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>",
      "video_note_url": "<video_note_url>"
    },
    "name": "send_video_note"
  }
}

Input Schema

Name	Required	Description
`chat_id`	Yes	Target chat ID.
`video_note_url`	Yes	URL or file_id of the video note.
`duration`	No	Duration in seconds.
`length`	No	Video width and height (diameter of the circle).
`disable_notification`	No	Send silently.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`error`	No
`message_id`	No
`chat_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedMay 3, 2026
- addedInput schema / properties / chat_id / description
```
Added value: +"Target chat ID."
```
- addedInput schema / properties / disable_notification / description
```
Added value: +"Send silently."
```
- addedInput schema / properties / duration / description
```
Added value: +"Duration in seconds."
```
- addedInput schema / properties / length / description
```
Added value: +"Video width and height (diameter of the circle)."
```
- addedInput schema / properties / video_note_url / description
```
Added value: +"URL or file_id of the video note."
```
First observedv0.7.1Mar 16, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description must convey behavioral traits but only states the action. No mention of permissions, side effects, or response behavior.

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?

One sentence, no wasted words. Front-loaded with purpose.

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?

Given the tool's low complexity and presence of output schema, the description is adequate but lacks context for error handling or prerequisites.

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%, so the schema already documents parameters. The description adds no extra meaning beyond the schema.

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 description states 'Send a video note (round video) to a Telegram chat,' clearly specifying the action and resource, and distinguishes it from other send tools by mentioning the 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 on when to use this tool versus alternatives like send_video or send_photo. The description lacks context for selection.

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