Skip to main content
Glama

send_sticker

Send a sticker to a Telegram chat using file ID or URL. Control silent sending with the disable_notification option.

Instructions

Send a sticker to a Telegram chat.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chat_idYesTarget chat ID.
stickerYesFile ID or URL of the sticker (WEBP/TGS/WEBM).
disable_notificationNoSend silently.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
errorNo
message_idNo
chat_idNo

Implementation Reference

  • The main handler function for the 'send_sticker' tool. It validates chat permissions, acquires rate limiter, calls bot.send_sticker(), and returns a SendMediaResult. Registered via @mcp.tool decorator inside register_media_tools().
    async def send_sticker(
        chat_id: int,
        sticker: str,
        disable_notification: bool = False,
    ) -> SendMediaResult:
        """Send a sticker to a Telegram chat.
    
        Args:
            chat_id: Target chat ID.
            sticker: File ID or URL of the sticker (WEBP/TGS/WEBM).
            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_sticker",
                    {"chat_id": chat_id, "sticker": sticker},
                    result.ok,
                    result.error,
                )
            return result
    
        try:
            if ctx.rate_limiter:
                await ctx.rate_limiter.acquire()
            msg = await ctx.bot.send_sticker(
                chat_id=chat_id,
                sticker=sticker,
                disable_notification=disable_notification,
            )
            result = SendMediaResult(ok=True, message_id=msg.message_id, chat_id=msg.chat.id)
        except (TelegramBadRequest, TelegramForbiddenError) as exc:
            result = SendMediaResult(ok=False, error=str(exc))
    
        if ctx.audit_logger:
            ctx.audit_logger.log(
                "send_sticker",
                {"chat_id": chat_id, "sticker": sticker},
                result.ok,
                result.error,
            )
        return result
  • The SendMediaResult response model used as the return type for send_sticker. Contains optional message_id and chat_id fields.
    class SendMediaResult(ToolResponse):
        message_id: int | None = None
        chat_id: int | None = None
  • The conditional registration of 'send_sticker' as an MCP tool inside register_media_tools(). It checks if allowed_tools is None or contains 'send_sticker'.
    if allowed_tools is None or "send_sticker" in allowed_tools:
    
        @mcp.tool
        async def send_sticker(
  • Permission mapping for 'send_sticker' - it requires MESSAGING permission level.
    "send_sticker": PermissionLevel.MESSAGING,
Behavior2/5

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

No annotations are provided, so the description must carry the burden. It does not disclose any behavioral traits such as what happens if the sticker file is invalid, size limits, or whether the sticker is sent immediately or queued.

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 concise sentence. It is front-loaded with the key action and resource. However, it could be slightly more informative without being verbose.

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?

Given the richness of sibling tools, the description is too sparse. It does not mention the output schema or any return values, and does not provide enough detail to guide an agent in correct invocation, especially for a tool with 3 parameters and no annotations.

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?

The input schema covers all three parameters with descriptions (100% coverage). The description adds no additional meaning beyond the schema, so it meets the baseline but provides no extra value.

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) and the resource (sticker) and target (Telegram chat). It is specific enough to distinguish from sibling tools like send_document or send_photo, but lacks any additional context about sticker formats or behavior.

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?

The description provides no guidance on when to use this tool over alternatives (e.g., send_document for sticker files) or any prerequisites. It simply states the action without context.

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