Skip to main content
Glama
EvandroSchechtel

WhatsApp Business MCP Server

send_contact_message

Send contact cards to WhatsApp numbers using the WhatsApp Business API. Share contact information including names, phone numbers, and emails through automated messaging.

Instructions

Send a contact card to a WhatsApp number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRecipient phone number
contactsYesArray of contact cards to send

Implementation Reference

  • The implementation of the logic to send a contact message via the WhatsApp API.
    async sendContactMessage(to: string, contacts: unknown[]) {
      return this.request(`/${this.config.phoneNumberId}/messages`, "POST", {
        messaging_product: "whatsapp",
        to,
        type: "contacts",
        contacts,
      });
    }
  • The input schema for the send_contact_message tool.
    {
      to: z.string().describe("Recipient phone number"),
      contacts: z
        .array(
          z.object({
            name: z.object({ formatted_name: z.string(), first_name: z.string().optional() }),
            phones: z.array(z.object({ phone: z.string(), type: z.string().optional() })).optional(),
            emails: z.array(z.object({ email: z.string(), type: z.string().optional() })).optional(),
          })
        )
        .describe("Array of contact cards to send"),
    },
  • src/index.ts:249-268 (registration)
    The registration of the send_contact_message MCP tool.
    server.tool(
      "send_contact_message",
      "Send a contact card to a WhatsApp number.",
      {
        to: z.string().describe("Recipient phone number"),
        contacts: z
          .array(
            z.object({
              name: z.object({ formatted_name: z.string(), first_name: z.string().optional() }),
              phones: z.array(z.object({ phone: z.string(), type: z.string().optional() })).optional(),
              emails: z.array(z.object({ email: z.string(), type: z.string().optional() })).optional(),
            })
          )
          .describe("Array of contact cards to send"),
      },
      async ({ to, contacts }) =>
        executeWithHooks("send_contact_message", { to, contacts }, config, () =>
          wa.sendContactMessage(to, contacts)
        )
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('send') but doesn't reveal whether this is a mutating operation (likely yes), what permissions are required, whether it's synchronous/asynchronous, error conditions, or what happens on success/failure. For a messaging tool with zero annotation coverage, this is a significant gap.

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, efficient sentence that front-loads the core purpose with zero wasted words. It immediately communicates what the tool does without unnecessary elaboration.

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 this is a mutating tool (sending messages) with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like success responses, error handling, authentication needs, or rate limits. The agent lacks critical context for proper invocation.

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%, with both parameters ('to' and 'contacts') clearly documented in the schema. The description adds no additional parameter semantics beyond implying the 'contacts' parameter contains contact cards. This meets the baseline of 3 when the schema does the heavy lifting.

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 resource ('contact card to a WhatsApp number'), making the purpose immediately understandable. It distinguishes this from other messaging tools (like send_text_message or send_media_message) by specifying it's for contact cards. However, it doesn't explicitly differentiate from all siblings (e.g., send_interactive_message might also involve contacts).

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. It doesn't mention prerequisites (e.g., needing WhatsApp Business API access), when contact cards are appropriate versus text messages, or any constraints like rate limits. The agent must infer usage from the tool name alone.

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/EvandroSchechtel/mcp-whatsapp'

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