Skip to main content
Glama
billyfranklim1

mcp-evolution

Send Sticker

send_sticker

Send a sticker message to a WhatsApp recipient. Provide the recipient's phone number and the sticker as a URL or base64-encoded webp image.

Instructions

Send a sticker message via the pinned WhatsApp instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesRecipient JID or phone number (e.g. 5511999999999 or group@g.us)
stickerYesURL or base64 of the sticker (webp format)

Implementation Reference

  • Import of registerSendSticker from the send-sticker module into the tools registry.
    import { registerSendSticker } from "./send-sticker.js";
  • Registration call that wires registerSendSticker into the MCP server during startup.
    registerSendSticker(server, client);
  • The registerSendSticker function which registers the 'send_sticker' tool on the MCP server. The handler calls the Evolution API endpoint /message/sendSticker/{instanceName} with number and sticker arguments.
    export function registerSendSticker(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "send_sticker",
        {
          title: "Send Sticker",
          description: "Send a sticker message via the pinned WhatsApp instance.",
          inputSchema: schema,
        },
        async (args) => {
          try {
            const data = await client.post(`/message/sendSticker/${client.instanceName}`, {
              number: args.number,
              sticker: args.sticker,
            });
            return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
          } catch (e) {
            if (e instanceof McpError) return { isError: true, content: [{ type: "text" as const, text: e.message }] };
            throw e;
          }
        }
      );
    }
  • Input schema for send_sticker: number (PhoneOrJidSchema) and sticker (URL or base64 webp string).
    const schema = {
      number: PhoneOrJidSchema,
      sticker: z.string().min(1).describe("URL or base64 of the sticker (webp format)"),
    };
  • PhoneOrJidSchema used as the type for the 'number' input parameter in the send_sticker schema.
    export const PhoneOrJidSchema = z
      .string()
      .min(1)
      .describe("Recipient JID or phone number (e.g. 5511999999999 or group@g.us)");
Behavior2/5

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

No annotations provided; the description does not disclose any behavioral traits such as error handling, required authentication, or rate limits.

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?

Single sentence is concise and front-loaded, but could include more context without becoming 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?

Description is too minimal for a tool with no output schema and no annotations; it omits details like sticker format requirements or result feedback.

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%, and the schema already details the parameters. The description adds no additional 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 clearly states the action (send) and the object (sticker message), distinguishing it from sibling tools like send_media or send_image.

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_media for other formats), or prerequisites like instance connection.

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/billyfranklim1/mcp-evolution'

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