Skip to main content
Glama
billyfranklim1

mcp-evolution

Send Status

send_status

Post text, image, video, or audio as a WhatsApp Status update to specified contacts or all contacts.

Instructions

Post a WhatsApp Status update (story) via the pinned instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesStatus content type
contentYesText content or URL/base64 of the media
captionNoCaption for media statuses
backgroundColorNoBackground color hex for text statuses (e.g. #000000)
fontNoFont style 0-4 for text statuses
statusJidListNoSpecific JIDs to send status to (omit for all contacts)

Implementation Reference

  • The registerSendStatus function registers the 'send_status' tool on the MCP server. The handler builds a payload from user arguments (type, content, caption, backgroundColor, font, statusJidList) and calls client.post() to POST to the Evolution API endpoint /message/sendStatus/{instanceName}. It returns the API response as text content, or an error if the request fails.
    export function registerSendStatus(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "send_status",
        {
          title: "Send Status",
          description: "Post a WhatsApp Status update (story) via the pinned instance.",
          inputSchema: schema,
        },
        async (args) => {
          try {
            const payload: Record<string, unknown> = {
              type: args.type,
              content: args.content,
            };
            if (args.caption !== undefined) payload["caption"] = args.caption;
            if (args.backgroundColor !== undefined) payload["backgroundColor"] = args.backgroundColor;
            if (args.font !== undefined) payload["font"] = args.font;
            if (args.statusJidList !== undefined) payload["statusJidList"] = args.statusJidList;
            const data = await client.post(`/message/sendStatus/${client.instanceName}`, payload);
            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 the 'send_status' tool. Defines fields: type (enum: text/image/video/audio), content (string, required), caption (optional string), backgroundColor (optional hex string), font (optional int 0-4), and statusJidList (optional array of strings for specific JIDs).
    const schema = {
      type: z.enum(["text", "image", "video", "audio"]).describe("Status content type"),
      content: z.string().min(1).describe("Text content or URL/base64 of the media"),
      caption: z.string().optional().describe("Caption for media statuses"),
      backgroundColor: z.string().optional().describe("Background color hex for text statuses (e.g. #000000)"),
      font: z.number().int().min(0).max(4).optional().describe("Font style 0-4 for text statuses"),
      statusJidList: z.array(z.string()).optional().describe("Specific JIDs to send status to (omit for all contacts)"),
    };
  • Registration call in registerAllTools(): invokes registerSendStatus(server, client) to register the send_status tool during server initialization.
    registerSendStatus(server, client);
  • Import of registerSendStatus from './send-status.js' in the tools index file.
    import { registerSendStatus } from "./send-status.js";
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states 'Post' (a write operation) but does not detail effects (e.g., replaces previous status, visibility, expiration), authentication requirements, or rate limits. The description is too sparse given the lack of annotations.

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 a single concise sentence with no extraneous words. It directly states the tool's purpose without redundancy.

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?

Despite 6 parameters and no output schema, the description provides minimal context. It does not explain key aspects like visibility to contacts, that statuses are ephemeral, or how parameters like statusJidList affect delivery. The schema covers parameter structure but the description should add high-level context.

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 description coverage is 100%, so baseline is 3. The description does not add any parameter-level context beyond what the schema already provides. It does not compensate for any gaps.

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 ('Post') and the resource ('WhatsApp Status update (story)'), and specifies it is 'via the pinned instance', which distinguishes it from other send_ tools that send to chats.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for status updates, but does not explicitly guide when to use it versus other send_ tools (e.g., send_media, send_text) or provide exclusions. The purpose is clear but lacks explicit comparative guidance.

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