Skip to main content
Glama
EvandroSchechtel

WhatsApp Business MCP Server

get_business_profile

Retrieve WhatsApp Business profile details including about text, address, description, email, websites, and profile picture for account management.

Instructions

Get the WhatsApp Business profile (about, address, description, email, websites, profile picture).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the request to retrieve the WhatsApp business profile.
    async getBusinessProfile() {
      return this.request(
        `/${this.config.phoneNumberId}/whatsapp_business_profile?fields=about,address,description,email,profile_picture_url,websites,vertical`
      );
    }
  • src/index.ts:341-349 (registration)
    Registration of the get_business_profile MCP tool.
    server.tool(
      "get_business_profile",
      "Get the WhatsApp Business profile (about, address, description, email, websites, profile picture).",
      {},
      async () =>
        executeWithHooks("get_business_profile", {}, config, () =>
          wa.getBusinessProfile()
        )
    );
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Get' implies a read-only operation, it doesn't explicitly state this is safe/non-destructive, mention authentication requirements, rate limits, error conditions, or what happens if the profile doesn't exist. It provides minimal behavioral context beyond the basic operation.

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 immediately states the tool's purpose and enumerates the returned fields. Every word contributes value with no redundancy or unnecessary elaboration. It's perfectly front-loaded and appropriately sized for this simple retrieval tool.

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?

For a zero-parameter read tool with no output schema, the description adequately covers what information is retrieved. However, it lacks details about the return format (structure, data types), potential errors, or authentication requirements. Given the simplicity of the tool, the description is minimally complete but could benefit from slightly 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?

The tool has zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters, maintaining focus on what the tool returns. This meets the baseline expectation for zero-parameter tools.

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 ('Get') and the resource ('WhatsApp Business profile'), and lists specific profile fields (about, address, description, email, websites, profile picture). It distinguishes this read operation from sibling tools like update_business_profile, but doesn't explicitly contrast with other read tools like get_analytics or get_phone_numbers.

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, appropriate contexts, or compare it to other profile-related tools like update_business_profile. The agent must infer usage from the tool name and description 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