Skip to main content
Glama
Jem-HR
by Jem-HR

send_sticker

Send sticker messages via WhatsApp Business API using webp format stickers to specified recipients, with optional reply functionality.

Instructions

Send a sticker message.

Args: to: Phone number or WhatsApp ID sticker: Sticker URL or media ID (must be webp format) reply_to_message_id: Message ID to reply to

Returns: Dictionary with success status and message ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYes
stickerYes
reply_to_message_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The send_sticker handler function - decorated with @mcp.tool(), accepts 'to', 'sticker', and optional 'reply_to_message_id' parameters, calls wa_client.send_sticker() to send the sticker, and returns success status with message ID
    @mcp.tool()
    async def send_sticker(
        to: str,
        sticker: str,
        *,
        reply_to_message_id: Optional[str] = None,
    ) -> dict:
        """
        Send a sticker message.
        
        Args:
            to: Phone number or WhatsApp ID
            sticker: Sticker URL or media ID (must be webp format)
            reply_to_message_id: Message ID to reply to
        
        Returns:
            Dictionary with success status and message ID
        """
        try:
            result = wa_client.send_sticker(
                to=to,
                sticker=sticker,
                reply_to_message_id=reply_to_message_id,
            )
            
            logger.info(f"Sticker sent to {to}")
            message_id = getattr(result, 'id', str(result)) if result else None
            return {"success": True, "message_id": message_id}
        except Exception as e:
            logger.error(f"Failed to send sticker: {str(e)}")
            return {"success": False, "error": str(e)}
  • The register_messaging_tools function that registers all messaging tools including send_sticker with the MCP server
    def register_messaging_tools(mcp, wa_client: WhatsApp):
        """Register all messaging-related tools."""
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'send' implies a write operation, the description doesn't cover important behavioral aspects: whether this requires specific permissions, rate limits, authentication needs, what happens if the sticker URL is invalid, whether the message is ephemeral or persistent, or error conditions. The return value mention is helpful but minimal.

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: a clear purpose statement followed by organized parameter explanations and return value information. Every sentence earns its place, with no redundant information. The Args/Returns formatting makes it easy to scan while maintaining complete information.

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 3 parameters with 0% schema coverage and no annotations, the description does a reasonable job but has gaps. The output schema exists (mentioned in Returns), so describing return values isn't needed. However, for a messaging tool with behavioral implications and multiple similar siblings, more context about when/why to use stickers would improve completeness. The parameter explanations are good but could benefit from more behavioral context.

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 adds significant value by explaining all three parameters: 'to' as phone number or WhatsApp ID, 'sticker' as URL or media ID with format constraint (webp), and 'reply_to_message_id' as optional reply target. This compensates well for the schema's lack of descriptions, though it doesn't cover all edge cases or provide examples.

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 verb 'send' and the resource 'sticker message', making the purpose immediately understandable. It distinguishes this tool from other messaging tools like send_message or send_image by specifying it's for stickers specifically. However, it doesn't explicitly differentiate from all siblings like send_template or send_video beyond the sticker focus.

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 versus alternatives. With multiple messaging siblings (send_message, send_image, send_video, send_audio, send_document, send_template), there's no indication of when a sticker is appropriate versus other message types. No prerequisites, exclusions, or context for choosing stickers over other content types are mentioned.

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/Jem-HR/pywa-mcp-server'

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