Telegram Notifier MCP Server

Send Telegram Photo

send_telegram_photo

Send a photo to a Telegram chat with optional formatted caption. Supports file path, URL, or base64 image.

Instructions

Send a photo/image via Telegram bot

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": {
      "photo": "<photo>"
    },
    "name": "send_telegram_photo"
  }
}

Input Schema

Name	Required	Description	Default
`photo`	Yes	File path, HTTP URL, or base64 encoded image data
`caption`	No	Photo caption with formatting support
`parseMode`	No	Caption formatting mode	MarkdownV2

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.6Jun 14, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided, so description must fully disclose behavior. It only states it sends a photo, with no information about side effects, permissions, rate limits, or error handling.

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?

The description is a single sentence with no unnecessary information. It is front-loaded but could benefit from a second sentence addressing common constraints.

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?

No output schema, no annotations, and no description of return values or error conditions make the tool definition incomplete for an agent to understand full behavior.

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 description adds minimal value beyond what the schema already provides. The description does not clarify the photo parameter types beyond the schema's enumeration.

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 tool sends a photo/image via Telegram bot, distinguishing it from sibling tools like send_telegram_document or send_telegram_video. However, it lacks specifics like supported file formats or size limits.

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 (e.g., send_markdown_message_as_telegram_bot, send_telegram_document). No mention of prerequisites or context.

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

Deploy Server