Skip to main content
Glama
billyfranklim1

mcp-evolution

Send List

send_list

Send an interactive list message to a WhatsApp number or group, with a title, description, button text, and sections of rows for user selection.

Instructions

Send a WhatsApp list message (interactive menu) via the pinned instance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberYesRecipient JID or phone number (e.g. 5511999999999 or group@g.us)
titleYesMessage title
descriptionYesMessage body/description
buttonTextYesText on the list button (e.g. 'View Options')
footerTextNoOptional footer text
sectionsYesList sections, each with rows

Implementation Reference

  • Main handler function registerSendList that registers the 'send_list' tool. Builds a payload with number, title, description, buttonText, sections, and optional footerText, then POSTs to /message/sendList/{instanceName}.
    export function registerSendList(server: McpServer, client: EvolutionClient): void {
      server.registerTool(
        "send_list",
        {
          title: "Send List",
          description: "Send a WhatsApp list message (interactive menu) via the pinned instance.",
          inputSchema: schema,
        },
        async (args) => {
          try {
            const payload: Record<string, unknown> = {
              number: args.number,
              title: args.title,
              description: args.description,
              buttonText: args.buttonText,
              sections: args.sections,
            };
            if (args.footerText) payload["footerText"] = args.footerText;
            const data = await client.post(`/message/sendList/${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 send_list: defines RowSchema (title, description, rowId), SectionSchema (title, rows), and the top-level input schema (number, title, description, buttonText, footerText, sections).
    const RowSchema = z.object({
      title: z.string().min(1),
      description: z.string().optional(),
      rowId: z.string().optional(),
    });
    
    const SectionSchema = z.object({
      title: z.string().min(1),
      rows: z.array(RowSchema).min(1),
    });
    
    const schema = {
      number: PhoneOrJidSchema,
      title: z.string().min(1).describe("Message title"),
      description: z.string().min(1).describe("Message body/description"),
      buttonText: z.string().min(1).describe("Text on the list button (e.g. 'View Options')"),
      footerText: z.string().optional().describe("Optional footer text"),
      sections: z.array(SectionSchema).min(1).describe("List sections, each with rows"),
    };
  • Import of registerSendList from send-list.ts.
    import { registerSendList } from "./send-list.js";
  • Invocation of registerSendList(server, client) to register the tool on the MCP server.
    registerSendList(server, client);
  • PhoneOrJidSchema used by send_list's input schema for the 'number' field.
    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 are provided, so the description should disclose behavioral traits. It only mentions 'via the pinned instance' but does not specify what happens if the instance is not pinned, required authentication, rate limits, or whether the operation is synchronous.

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 sentence that is appropriately sized and front-loaded with the core purpose. No unnecessary words.

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 complexity of the tool (6 parameters, no output schema, no annotations), the description lacks crucial context such as return values, error handling, or any behavioral details beyond the bare minimum.

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 schema has 100% description coverage, so the baseline is 3. The description does not add value beyond the schema; it repeats the parameter names without explaining the structure of sections or providing examples.

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 verb 'send', the resource 'WhatsApp list message (interactive menu)', and specifies 'via the pinned instance', which differentiates it from sibling tools like send_text or send_button.

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 such as send_button or send_poll. No explicit context for when/not to use is given.

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